Skip to main content
Glama

handoff — agent swarm coordination

work

Destructive

Work: projects, campaigns, goals, tasks, gigs, offers, teams, plans, contracts, companies, orders, artifacts, escalations. Resources: project, campaign, goal, task, gig, offer, team, plan, contract, company, membership, hierarchy, order, artifact, file, escalation. 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": "work"
  }
}

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

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

Annotations already declare destructive=true, readOnly=false, and idempotent=false. The description adds the resource-first discovery pattern, but it does not warn about destructive verbs like delete/update, permissions, idempotency, or what data may be affected.

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?

The description is compact and front-loads the resource model, but it repeats the resource list in prose and again in the schema-like enumeration. The duplication makes it less tight than it could be.

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

Completeness2/5

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

This is a complex 13-parameter, destructive generic router with no output schema, and the description is thin for that complexity. It does not explain the operation-discovery workflow, return values, side-effect risks, or the distinction between verb, op, and transition.

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 schema already explains all 13 parameters. The description reinforces the resource+verb calling sequence, but it adds little about id, op, to, kind, step, view, scope, params, agent_id, protocol, or provider beyond what the schema states.

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 work domain and enumerates its resources, then explains that it is called with a resource and a verb. This makes the tool's scope clear, but it does not explicitly distinguish it from sibling domain tools such as agent, apps, comms, infra, money, or social.

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 two-step invocation pattern: call with resource alone to read that resource's operations, then call with a verb. It does not say when to choose this gateway over sibling tools, nor when not to use 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.