Skip to main content
Glama

Handover

by sh.handover
OverviewDiscussionsAdmin

Create a handover

handover.create

Create durable shared context with an initial immutable revision. Authorship comes from the authenticated Handover identity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoFree-form continuation note recorded in the initial revision.
briefNoStructured continuation brief for humans and agents.
titleYesShort, specific name for the durable context.
summaryNoConcise explanation of what this handover contains.
artifactsNoFiles attached to the initial immutable revision.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / properties / artifacts / description
      Added value: +"Files attached to the initial immutable revision."
    • addedInput schema / properties / brief / description
      Added value: +"Structured continuation brief for humans and agents."
    • 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 / note / description
      Added value: +"Free-form continuation note recorded in the initial revision."
    • addedInput schema / properties / summary / description
      Added value: +"Concise explanation of what this handover contains."
    • addedInput schema / properties / title / description
      Added value: +"Short, specific name for the durable context."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations are all false, providing little positive safety info. The description adds useful behavioral context: the initial revision is immutable, and authorship comes from the authenticated Handover identity, which is not captured in annotations. It does not mention failure modes, but covers key behavioral traits beyond the schema.

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 two dense sentences, front-loaded with the action. Every word contributes meaning; no redundancy or filler.

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

Completeness3/5

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

The schema is complex with nested objects and anyOf conditions, but the description is brief. It does not mention the return value (no output schema), the requirement to provide note/brief/artifacts, or how this tool relates to other handover operations. While adequate, it leaves gaps in an otherwise complex tool.

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 documents all parameters in detail. The tool description does not add extra parameter guidance, so the baseline score of 3 is appropriate.

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 (Create) and resource (durable shared context), and adds the distinctive 'initial immutable revision' aspect, which differentiates it from sibling tools like handover.continue or handover.publish.

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?

The description implies you should use this tool to create a new handover context, but it does not explicitly say when to use it versus alternatives such as handover.continue or handover.publish. It also lacks exclusion criteria or alternative recommendations.

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