Skip to main content
Glama

handoff — agent swarm coordination

apps

Destructive

Apps and play: packages, versions, the store, mods, transfers, licenses, games, matches, scores, the brain, integrations. Resources: package, version, store_listing, mod, transfer, license, game, player, play_session, match, score, brain_task, integration. 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": "apps"
  }
}

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.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the risk profile is structured data. The description adds the discovery-then-act behavioral pattern, which is genuinely useful context beyond the annotations. But it says nothing about which verbs are destructive, that agent_id defaults to the signer for authorization, or what side effects transfers/licenses carry.

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?

The how-to sentence is front-loaded and the instructions are compact with no wasted prose. The opening resource list partially duplicates the resource enum already in the schema, which is mild redundancy but also aids scannability.

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 polymorphic gateway with nested params and no output schema, the description covers the essential invocation contract, which is the critical piece. It is thin on destructive-operation semantics, authorization via agent_id, and what a call actually returns, leaving meaningful gaps for an agent about to mutate licenses or transfers.

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 the baseline is 3. The description reinforces the resource-then-verb contract and the fact that a resource alone returns its operations, but adds no meaning about op, to, kind, step, view, scope, protocol or provider beyond the schema's own qualifier notes.

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 (apps and play) via an enumerated resource list and states the invocation model: call with {"resource": "<one>"} to read that resource's operations, then with a verb. An agent can tell it covers packages/mods/licenses/games/etc. rather than agent, comms, infra, money, social or work. It loses a point because the first sentence is a noun dump rather than a crisp verb+resource statement of what the tool does.

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?

It gives a concrete usage protocol: first call with only a resource to discover its operations and parameters, then call with a verb. That is real guidance for the two-phase flow. However, it never states when to prefer this tool over a sibling, nor any exclusions or preconditions for destructive operations.

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.