Skip to main content
Glama

Generate Handoff

generate_handoff

Create a session summary of completed work, next steps, project state, and known issues so another AI can continue the project without losing context.

Instructions

Generate a session summary capturing what was done, what's next, and current project state for handoff to another AI.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
known_issuesNoAny bugs or issues the next session should know about.
session_summaryNoBrief summary of what was accomplished this session.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the composition of the summary (done / next / state), but omits whether the result is persisted to disk, whether existing handoffs are overwritten, and whether the context store must be initialized first — the 'path: Project root directory' parameter hints at file writes but the description never confirms it.

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?

A single sentence that front-loads the action and enumerates the three content components without filler. Nothing is redundant and no sentence fails to earn its place.

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?

An output schema exists, so return-value explanation is not required, and the three inputs are fully documented in the schema. What remains missing is whether the tool mutates persisted state (writes a handoff file) and any prerequisite on context being populated — modest but non-trivial omissions for a tool with no annotations.

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 all three parameters (path, known_issues, session_summary) are already documented in the schema, making 3 the baseline. The description adds no syntax, format, or interaction guidance for these inputs 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?

States a specific verb ('Generate') and a specific artifact ('a session summary capturing what was done, what's next, and current project state') with an explicit consumer ('another AI'). It is distinguishable from siblings like get_last_handoff and list_handoffs, though it never names those siblings or clarifies how it differs from end_session.

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?

Usage is only implied by the phrase 'for handoff to another AI' — an agent can infer this is called at the end of a work session. There is no explicit when-to-use, no when-not-to-use, and no pointer to get_last_handoff / list_handoffs / end_session as alternatives, which is a real gap in a crowded context/handoff sibling cluster.

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