Tools and MCP servers

{
  "config": {
    "name": "Research a company",
    "tools": [{ "tool_id": "3f8b0f4c-9a1e-4a7d-9c2b-1d5e6f70a821" }],
    "mcps": [{ "integration_id": "c41d8e37-25a9-4f60-b3d8-9e07a15c4b62" }],
    "output": [
      { "name": "summary", "type": "string", "description": "Two sentences on what they sell." }
    ]
  }
}

​

Attaching tools

• Only published tools attach. An unpublished tool is refused when the task is saved. See testing and publishing.
• No tool containing a handoff operation. A task returns to whoever entered it, so it cannot hand the conversation on; such a tool is refused at publish.
• Inline tools become real tools. A {"tool": {…}} entry is created as a stored tool, published as version 1, and replaced by its {"tool_id": "…"} in the saved config. A name already used in the workspace is a 409. Inline FAQs under faqs follow the same rule.

{
  "tools": [
    {
      "tool": {
        "name": "get_order",
        "description": "Fetch one order by its id.",
        "json_schema": {
          "type": "object",
          "properties": { "order_id": { "type": "string" } },
          "required": ["order_id"]
        },
        "operations": [
          {
            "kind": "http",
            "config": {
              "method": "GET",
              "url": "https://api.northwind.example/orders/{{args.order_id}}",
              "headers": { "Authorization": "Bearer {{secrets.NORTHWIND_KEY}}" }
            }
          }
        ]
      }
    }
  ]
}

​

Publishing pins tool versions

​

Attaching MCP servers

• allowed_tools lives on the integration, null meaning every tool. It is read live, not frozen by a publish, so narrowing it affects every task and agent on the next round.
• The model sees namespaced names. tools_namespace: "crm" turns search into crm_search; write prompts against the exposed name. Two attached servers sharing a namespace are refused at save.

​

Cost and the trace

​

Next