Skip to main content
Glama

Agent Handoff

by io.github.jordan23wagner-ops

handoff

Hand a message off to another agent. Cleans and normalizes the payload, stamps it with handoff metadata (id, timestamp, estimated tokens, target agent), and records the handoff. Use this when passing work or context from one agent to the next in a multi-agent pipeline. This is a metered, billable operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesThe payload to hand off. Accepts a plain string or a JSON object. Max 256 KB.
next_agentYesName/identifier of the agent receiving this handoff.

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description fully bears burden; discloses mutation (cleans, normalizes, records), metadata stamping, and billing. No contradictions.

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

Conciseness5/5

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

Four sentences, front-loaded with action, each adds value: operation, metadata, usage context, billing. No fluff.

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?

Given no output schema and moderate complexity, description covers operation, metadata, and usage well; could mention return or errors but not required.

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 coverage is 100% with both params described; description adds max size for message but little beyond schema, meeting baseline.

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

Purpose5/5

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

Uses specific verb 'hand off' plus resource 'another agent', details actions (cleans, normalizes, stamps metadata), and distinguishes from sibling tool get_usage_stats.

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?

Explicitly says 'Use this when passing work or context from one agent to the next in a multi-agent pipeline.' and mentions it is metered/billable; no explicit exclusions but sibling is for stats, no overlap.

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

All Agent Handoff toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one is read-only for retrieving usage stats, the other is a metered operation for performing a handoff. There is no overlap or ambiguity between them.

Naming Consistency4/5

Both tools use snake_case, but one is a verb (handoff) while the other is verb_noun (get_usage_stats). This minor inconsistency is offset by clear and predictable naming within a small set.

Tool Count5/5

With only two tools, the server is lean and focused on its single purpose—agent handoff. Every tool earns its place, and there is no bloat or deficiency given the narrow domain.

Completeness5/5

The tool surface covers the full lifecycle for the server's purpose: a read operation to inspect handoff history and a write operation to execute handoffs. No obvious gaps exist for this utility.

Resources