Skip to main content
Glama

Handover

by sh.handover
OverviewDiscussionsAdmin

Continue a handover

handover.continue

Append an immutable revision after reading the current snapshot. expectedRevisionId is mandatory to prevent overwriting another collaborator's work. Omitted artifacts are inherited; matching names are replaced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoWhat changed or what the next collaborator should know.
briefNoUpdated structured continuation brief.
artifactsNoNew or replacement files; omitted files remain inherited.
handoverIdYesHandover to continue after reading its current snapshot.
expectedRevisionIdYesCurrent revision ID returned by handover.get; prevents lost updates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / properties / artifacts / description
      Added value: +"New or replacement files; omitted files remain inherited."
    • addedInput schema / properties / brief / description
      Added value: +"Updated structured continuation brief."
    • addedInput schema / properties / brief / properties / currentState / description
      Added value: +"Verified state at the moment this revision is published."
    • addedInput schema / properties / brief / properties / decisions / description
      Added value: +"Decisions already made that successors should preserve."
    • addedInput schema / properties / brief / properties / nextSteps / description
      Added value: +"Concrete continuation steps for the receiving actor."
    • addedInput schema / properties / brief / properties / nextSteps / items / properties / id / description
      Added value: +"Optional stable identifier for this step."
    • addedInput schema / properties / brief / properties / nextSteps / items / properties / status / description
      Added value: +"Whether the step still needs action."
    • addedInput schema / properties / brief / properties / nextSteps / items / properties / text / description
      Added value: +"One actionable continuation step."
    • addedInput schema / properties / brief / properties / objective / description
      Added value: +"The outcome the next human or agent should continue toward."
    • addedInput schema / properties / brief / properties / openQuestions / description
      Added value: +"Unresolved questions that still require evidence or judgment."
    • addedInput schema / properties / expectedRevisionId / description
      Added value: +"Current revision ID returned by handover.get; prevents lost updates."
    • addedInput schema / properties / handoverId / description
      Added value: +"Handover to continue after reading its current snapshot."
    • addedInput schema / properties / note / description
      Added value: +"What changed or what the next collaborator should know."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only indicate non-read-only and non-idempotent, which is thin. The description adds crucial behavioral details: revisions are immutable, expectedRevisionId prevents overwriting, and artifact semantics are inherited/replaced. This goes well beyond what annotations provide.

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?

Three focused sentences with no filler. The first sentence gives the core action, the second explains the critical guard, and the third clarifies artifact inheritance.

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?

For a 5-param mutating tool with nested objects, the description covers the essential semantics: append, concurrency, artifact behavior. The schema handles parameter details, and no output schema exists, so return values aren't required. This is sufficient for correct selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters, so baseline 3. The description adds rationale for expectedRevisionId and explains artifact merging behavior, which enriches the schema's technical descriptions.

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 the action (append), the resource (immutable revision to a handover), and the required prerequisite (reading the current snapshot). It distinguishes itself from sibling tools like handover.create by emphasizing continuation and concurrency protection.

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?

It explicitly instructs that the tool is used after reading the current snapshot, and explains the purpose of expectedRevisionId as a lock against lost updates. While it doesn't name alternative tools, the workflow is clear enough for an agent to choose it appropriately.

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

All Handover toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources