Skip to main content
Glama

handoff — agent swarm coordination

infra

Destructive

The broker and what agents run on: health, coordinators, tunnels, domains, DNS, push. Resources: broker, coordinator, tunnel, domain, dns_record, push_subscription. 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": "infra"
  }
}

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

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds one genuinely non-obvious behavior — that a resource-only call is a discovery read that returns available operations — which is valuable context beyond the annotations. It does not, however, flag that verbs like delete are destructive or describe any confirmation/auth implications, which matters for a tool annotated destructive.

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

Conciseness3/5

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

Three short sentences with no filler, and the resource list is front-loaded. The phrasing is telegraphic to the point of ambiguity — "what agents run on" and "then with a verb" require interpretation, and the two-phase call pattern is buried at the end rather than leading.

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?

For a 13-parameter generic dispatcher with no output schema, the definition covers the resource taxonomy and the discovery-then-act pattern, which is the minimum an agent needs to start. It omits what a call actually returns, how destructive verbs behave, and whether confirmation is expected — gaps that matter given destructiveHint=true. Adequate but with clear holes.

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% and all 13 parameters are documented, including the qualifier semantics of id/op/to/kind/step/view/scope, so the schema carries the heavy lifting. The description reinforces the resource-only discovery pattern, but that same point is already stated in the resource enum's own schema description, so the added meaning is marginal. Baseline 3 applies.

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

Purpose3/5

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

The description names the domain ("the broker and what agents run on") and enumerates the six resources it dispatches to, which lets an agent tell it apart from siblings like money or comms. But it never states a concrete verb+outcome — "infra" plus a resource list tells you the subject area, not what calling it accomplishes. The purpose is inferable 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?

There is real procedural guidance: call with {"resource": "<one>"} to read that resource's operations, then call again with a verb. That is a usable invocation protocol an agent would not otherwise guess. However, there is no guidance on when to choose this tool versus siblings, no mention of when not to use it, and no signal about which verb is appropriate in which situation.

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.