Tools
A tool is an operation an agent can request through its harness. A tool can read a calendar, search records, or submit data to a service. A tool’s input and output contract gives the harness a way to validate the request and return evidence to the run.
Declare an operation
Section titled “Declare an operation”Inputs and scope
Section titled “Inputs and scope”Expose a tool with a name, input contract, and an operation the harness can authorize. The model selects a tool and supplies arguments. Validate the arguments and resolve the current workspace binding before acting. Tool results return to the harness as data that a later step can use.
Example Studio requirement
Section titled “Example Studio requirement”A Studio connector tool resolves through this requirement in the Meeting desk fixture. The operation ID must also appear on the step that invokes it.
{ "id": "calendar", "label": "Google Calendar", "context": "personal", "providers": [ "googlecalendar" ], "operations": [ "upcoming" ], "optional": false}Dispatch and return results
Section titled “Dispatch and return results”- Resolve the declared tool in the running context and check the caller’s grant.
- Validate or map its arguments, then classify the effect from the supported operation.
- For a protected action, hold execution for the configured review and verify the approved proposal at dispatch.
- Return the projected result or a clear blocked or failed status. Record a receipt when an external effect occurred.
A playbook may expose an operation through MCP. MCP discovery and input schemas describe the tool. The current workspace, binding and approval still govern a real call.
See connector operations, approvals, and MCP interoperability.