Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Set an agent's integrations

set_agent_integrations

Replace an agent's integration connections with a specified list; pass an empty list to remove all connections. Invalid or unauthorized workspace/environment connections are rejected.

Instructions

Replace the integration connections an agent can use with the given list, and return the agent's integrations afterwards. An empty list removes them all. Each integration is a connection key of the form <INTEGRATION>_<connection id>, e.g. SNOWFLAKE_my_connection, and must be a connection in the same workspace; the request is refused with 404 if any is not, and with 400 if any is limited to environments the agent is not allowed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>",
      "body": "<body>"
    },
    "name": "set_agent_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
agent_idYesThe id of the agent.
X-Orchestra-Account-IdNoAct on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2026.10.12-0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the crucial behavior that this is a full replacement (existing connections are dropped, and an empty list clears everything) plus the specific error contract with status codes. That is exactly the context an agent needs before invoking a mutation, well beyond what the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, with the destructive replace semantics front-loaded before format rules and error conditions. No filler or repetition of annotation values; every clause (empty-list behavior, key format, error codes) carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with an output schema, the description covers the mutation model, input format, validation rules, and error outcomes, while briefly noting what is returned. Nothing an agent would need to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema leaves the `integration` string undocumented, but the description specifies its composite format `<INTEGRATION>_<connection id>` with a worked example (`SNOWFLAKE_my_connection`) and the workspace/environment validity constraints that trigger 404/400. This fully compensates for the 67% schema description coverage on the parameter that matters most.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Replace the integration connections an agent can use with the given list') and adds the post-condition (returns the agent's integrations afterwards). The replace/full-overwrite framing cleanly separates it from the sibling list_agent_integrations, so an agent can pick between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage semantics: an empty list removes all connections, and each entry must be a connection in the same workspace. It also states the failure conditions (404 if a connection is out of workspace, 400 if environment-limited). It stops short of naming alternatives or stating when not to use it, but the replace semantics make the intent unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools