Skip to main content
Glama

Delimit Handoff Create

delimit_handoff_create

Create a structured handoff receipt when transitioning between agents, documenting completed tasks, pending items, blockers, and next steps so the receiving agent knows exactly what to do.

Instructions

Create a handoff receipt when transitioning between agents.

When to use: at the end of a session or before passing work to another model — documents what was done, what's pending, and what the next agent should do first. When NOT to use: for general session summary (use delimit_session_handoff) or to acknowledge a receipt (delimit_handoff_acknowledge).

Sibling contrast: delimit_session_handoff is venture-scoped summary; delimit_soul_capture is richer cross-model state; this is the structured per-agent handoff with explicit completed/ not-completed/blockers/scope fields.

Side effects: writes a new handoff receipt via ai.handoff_receipts.create_receipt. The receiving agent should later call delimit_handoff_acknowledge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blockersNoComma-separated blockers encountered.
in_scopeNoComma-separated in-scope items.
priorityNoP0 / P1 (default) / P2.P1
to_modelNoTarget model name or "any" (default).any
completedNoComma-separated completed items.
assumptionsNoComma-separated assumptions made.
next_actionNoFirst thing the receiving agent should do.
out_of_scopeNoComma-separated explicitly excluded items.
not_completedNoComma-separated items not completed (with reasons).
files_modifiedNoJSON list of {path, change_type, summary} dicts, or empty to auto-detect.
task_descriptionNoWhat the task was (one line).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv4.7.9
    • changedInput schema / properties / assumptions / description
      Previous value: -"Comma-separated assumptions made during work."New value: +"Comma-separated assumptions made."
    • changedInput schema / properties / completed / description
      Previous value: -"Comma-separated list of completed items."New value: +"Comma-separated completed items."
    • changedInput schema / properties / files_modified / description
      Previous value: -"JSON list of {path, change_type, summary} dicts, or empty for auto-detect."New value: +"JSON list of {path, change_type, summary} dicts, or empty to auto-detect."
    • changedInput schema / properties / in_scope / description
      Previous value: -"Comma-separated items that were in scope."New value: +"Comma-separated in-scope items."
    • changedInput schema / properties / next_action / description
      Previous value: -"What the receiving agent should do first."New value: +"First thing the receiving agent should do."
    • changedInput schema / properties / not_completed / description
      Previous value: -"Comma-separated list of items not completed (with reasons)."New value: +"Comma-separated items not completed (with reasons)."
    • changedInput schema / properties / out_of_scope / description
      Previous value: -"Comma-separated items explicitly excluded."New value: +"Comma-separated explicitly excluded items."
    • changedInput schema / properties / priority / description
      Previous value: -"P0/P1/P2."New value: +"P0 / P1 (default) / P2."
    • changedInput schema / properties / to_model / description
      Previous value: -"Target model (or \"any\")."New value: +"Target model name or \"any\" (default)."
  2. Addedv4.5.5

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond the annotations by disclosing the concrete side effect: 'writes a new handoff receipt via ai.handoff_receipts.create_receipt.' It also documents the expected lifecycle next step, stating 'The receiving agent should later call delimit_handoff_acknowledge.' This is consistent with readOnlyHint=false and destructiveHint=false.

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 well-structured with labeled sections: purpose, when to use, when not to use, sibling contrast, and side effects. Every sentence earns its place, and the core purpose is front-loaded before the usage guidance.

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?

Given the output schema exists and the description covers purpose, usage boundaries, sibling differentiation, side effects, and follow-up action, nothing essential is missing for an agent to invoke this tool correctly. It is complete for a write-oriented handoff tool with many optional fields.

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?

The schema already provides 100% description coverage for all 11 parameters, so the baseline is 3. The description adds only modest context by noting the 'explicit completed/not-completed/blockers/scope fields,' which is helpful but does not materially deepen parameter understanding beyond the schema.

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 opens with a specific verb-resource pair: 'Create a handoff receipt when transitioning between agents.' It clearly differentiates itself from sibling tools by naming delimit_session_handoff, delimit_soul_capture, and delimit_handoff_acknowledge in the sibling contrast.

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 explicitly states when to use ('at the end of a session or before passing work to another model'), when not to use ('for general session summary' or 'to acknowledge a receipt'), and names the exact alternative tools. This leaves no ambiguity for an agent deciding between related handoff tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server