Skip to main content
Glama

Record handoff summary

record_handoff_summary

Record a structured handoff summary with context, next steps, and blockers to transfer work between agents or reviewers.

Instructions

Purpose: Store a structured handoff packet for the next agent or human reviewer. When to use: call when pausing, finishing, or transferring a task. Inputs: workspace_id, from/to agents, summary, next steps, blockers, tested commands, remaining risks, next action, and template. Side effects: writes a handoff row. Output: handoff_id for future retrieval. Failure modes: invalid workspace or malformed list fields are rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoHandoff status such as open, closed, or blocked.open
summaryYesConcise summary of completed work and current state.
templateNoHandoff template name, usually standard.standard
blocked_onNoOptional blockers that prevent progress.
next_stepsNoOptional ordered next steps for the receiver.
next_actionNoSingle most important next action.
workspace_idYesWorkspace UUID where the handoff belongs.
to_agent_nameNoOptional intended receiving agent or role.
from_agent_nameYesAgent that is leaving the handoff.
remaining_risksNoKnown risks, caveats, or areas needing follow-up.
tested_commandsNoCommands already run to validate the work.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Since no annotations are provided, the description fully covers behavioral traits: 'Side effects: writes a handoff row', 'Output: handoff_id for future retrieval', and 'Failure modes: invalid workspace or malformed list fields are rejected'. This is comprehensive for a mutation tool.

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?

The description is structured with clear bullet points (Purpose, When to use, Inputs, Side effects, Output, Failure modes) and is very concise. Every sentence adds value and is front-loaded.

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

Completeness5/5

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

Given the 11 parameters with 100% schema coverage and existence of an output schema, the description covers purpose, usage, side effects, output, and failure modes. Nothing essential is missing.

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 baseline is 3. The description lists input parameters but does not add meaning beyond the schema's descriptions. No examples or formatting hints are provided.

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?

The description clearly states 'Store a structured handoff packet for the next agent or human reviewer' with specific verb and resource. It distinguishes from siblings like close_handoff_summary and list_handoff_summaries through its unique write operation.

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?

The description explicitly states 'call when pausing, finishing, or transferring a task' providing clear context. It does not mention when not to use or name alternatives, but the context is specific enough for an agent to decide.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/geondongkim/geond-agent-protocol'

If you have feedback or need assistance with the MCP directory API, please join our Discord server