Skip to main content
Glama

Deposit a briefing for your successor (paid, x402)

handoff_deposit

PAID: hand off context to a successor process: a typed briefing (done with evidence, not done, in flight, next). Anyone with the id reads it; kept 3 days. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.0100 USDC.

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": "handoff_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
doneNoWhat is DONE. EVERY entry must have confidence 'measured' with non-null evidence; otherwise this is refused, free, as HANDOFF_DONE_REQUIRES_MEASURED.
notDoneNoWhat is NOT done. May be measured or unverified.
inFlightNoWhat was IN FLIGHT at the cut -- neither finished nor abandoned.
pickUpFirstNoWhat the successor should do FIRST. Mandatory and non-empty: a briefing with no next action is not a handoff.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "done",
      -  "notDone",
      -  "inFlight",
      -  "pickUpFirst"
      -]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), it discloses the exact price ($0.0100 USDC), the seven accepted chains, a 3-day retention window, and the visibility model ('anyone with the id reads it'). It also surfaces the refusal condition HANDOFF_DONE_REQUIRES_MEASURED and the fact refusals are free, which is exactly the kind of cost/authorization context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The paid status, price, and payment mechanics are front-loaded and the tail (feedback endpoint, price restated) is short. It is dense but nearly every clause carries operational meaning; the trailing 'Read daily; no individual reply' is the least essential part.

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?

For a paid mutation tool with no output schema, the definition covers cost, payment flow, retention, and readership well enough to call correctly. The remaining gap is the success return value — the description implies an id is issued ('anyone with the id reads it') but never says that the call returns one.

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 every field, including the confidence/evidence coupling and the measured-only rule for 'done'. The description adds the plain-language framing of the four sections but no syntax, format, or constraint detail beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb+resource — 'hand off context to a successor process: a typed briefing' — and enumerates the four sections (done with evidence, not done, in flight, next). That is far more specific than the title or the name alone, and it clearly separates this from retrieval or storage siblings.

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 gives an actionable call sequence: call unpaid to get the price, pay via x402 in _meta['x402/payment'], then call again — plus a separate free feedback path. It does not name an alternative tool or an explicit when-not-to-use condition, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources