Skip to main content
Glama

handoff

Produces an engineer-requested handover or case status summary by reading declared state, decisions, constraints, and evidence references.

Instructions

Read the declared state, decisions, constraints and evidence references as a handoff, FOR THE ENGINEER. Requires engineer_asked=true, which you may pass only when they actually asked for a summary, a handover, or where the case stands. Never call it to refresh your own memory — use resume for that.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "case_id": "<case_id>"
    },
    "name": "handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes
engineer_askedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does most of it: it establishes that this is a read of already-declared material and discloses the hard precondition governing invocation. It does not say what happens on violation (error vs. ignored) or that handoffs may be subject to rating, which the rate_handoff sibling hints at, so it stops short of a 5.

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 sentences, no filler, and the audience and prohibition are front-loaded before the corrective alternative. Every sentence constrains behavior and none repeats the schema.

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 values need no explanation, and the one genuinely ambiguous parameter is fully covered. Minor gaps remain: whether a false engineer_asked causes an error, and whether the case must already be open.

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 description coverage is 0%, so the description has to compensate. It fully explains engineer_asked's meaning and the only lawful condition for setting it, but case_id's semantics (must reference an existing case, format) are left entirely to the schema title.

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 uses a specific verb (read) on a named resource set (declared state, decisions, constraints, evidence references) and states the intended consumer: the engineer, not the agent. It also implicitly separates itself from resume, so an agent can place it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit gate (engineer_asked=true only when the engineer actually asked for a summary, handover, or status), an explicit prohibition (never to refresh your own memory), and the correct alternative (resume). This is exactly the when/when-not/alternative structure that earns top marks.

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