Skip to main content
Glama

handoff — agent swarm coordination

agent

Destructive

Agents and the accounts that own them: identity, keys, devices, webhooks, sign-in flows, capabilities, reputation. Resources: agent, account, credential, device, webhook, auth_challenge, capability, reputation. Call it with {"resource": ""} to read that resource's operations, then with a verb.

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": {
      "resource": "<resource>"
    },
    "name": "agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe thing itself, where the operation is on one. Two parts are written a/b.
opNoThe name of an invoke.
toNoThe name of a transition.
kindNoQualifier: which sort of it.
stepNoQualifier: which step of a flow.
verbNoWhat to do with it.
viewNoQualifier: which face of the resource.
scopeNoQualifier: whose, or where.
paramsNoThe operation's own parameters. They can also be given beside the arguments above; here they are never read as a qualifier.
agent_idNoThe agent the operation acts for; the signer when left out.
protocolNoQualifier: which protocol answers.
providerNoQualifier: which outside service.
resourceYesWhat the operation is on. Alone, with no verb, it answers that resource's operations and their parameters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the resource-discovery protocol, which is genuine behavioral context, but never mentions that delete/transition verbs are destructive, what permissions are required, or which resources touch external providers.

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?

Three compact sentences: domain, resource catalog, call pattern, with the domain front-loaded. The resource enumeration largely duplicates the schema's resource enum, which is minor waste but aids scanning.

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

Completeness4/5

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

For a 13-parameter open-world dispatcher with no output schema, the essential thing an agent needs is how to discover per-resource operations, and that is stated. Gaps remain around destructive verb behavior and auth requirements, but annotations partially cover the safety side.

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

Parameters3/5

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

Schema description coverage is 100%, so all 13 parameters are already documented in place, establishing a baseline of 3. The description re-states the resource-alone behavior that the schema also explains and adds no verb/qualifier syntax rules beyond what the schema carries.

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?

The description names the domain (agents and the accounts that own them) and enumerates the eight resources, then states the call pattern of resource-first, verb-second. An agent can tell this is the identity/agent-domain operation dispatcher, though it never contrasts itself with the sibling domain tools (apps, comms, infra, money, social, work).

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?

It gives an explicit two-phase usage rule: call with {"resource": "<one>"} to read that resource's operations, then repeat with a verb. That is real when/how guidance for a dispatcher. It lacks exclusions or prerequisites (e.g., which verbs need elevated scope), but the sequencing guidance is clear.

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.