Skip to main content
Glama

Client: approve a new account's plan and start it

channel_plan_approve
DestructiveIdempotent

The agency approves Autopilot's plan for a newly connected account, which starts it: that account's change types are turned on for the client (unless its set-up says watch only), the set-up is widened when it didn't cover this kind of work, and the plan's expectations go into the expectations ledger. Only on the agency's say-so.

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": {
      "client": "<client>",
      "channel": "<channel>"
    },
    "name": "channel_plan_approve"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYesClient name from list_clients
channelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

With destructiveHint=true already declared, the description earns credit by saying exactly what is mutated: change types turned on, set-up widened, entries written to the expectations ledger, with the 'watch only' exception noted. It omits what happens on a second call or on failure, which matters for a destructive mutation.

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

Conciseness4/5

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

Front-loaded with the action and its consequence, then the three side effects in one tight enumeration. Dense but every clause carries information; the closing 'Only on the agency's say-so' adds a gating rule rather than padding.

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

Completeness3/5

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

Given no output schema, the description covers effects and the watch-only branch well, but leaves out preconditions (plan must exist, account must be connected) and return/failure behavior. For a destructive, non-reversible-feeling activation, that is an adequate but incomplete picture.

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

Parameters2/5

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

The description never mentions either parameter. With schema coverage at 50%, only `client` is documented ('Client name from list_clients') while `channel` is a bare seven-value enum with no explanation of what a channel means or that it must correspond to a connected account — the description does nothing to close that gap.

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

Purpose4/5

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

Specific verb+resource ('approves Autopilot's plan for a newly connected account') with the downstream effect ('which starts it') spelled out, so an agent knows this is the activation step, not a read or a draft. It stops short of naming the sibling plan tools (get/save/decline), so differentiation is inferred from naming rather than stated.

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

Usage Guidelines3/5

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

'Only on the agency's say-so' is a real gating instruction and 'newly connected account' scopes the situation, which implies the plan must already exist via channel_plan_save and be reviewed via channel_plan_get. However, no alternative is named and the prerequisites (account linked, plan generated) are never made explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.