Skip to main content
Glama

delimit_handoff_create

Create a structured handoff receipt documenting completed tasks, pending items, blockers, and next actions to transfer work between agents.

Instructions

Create a handoff receipt when transitioning between agents (Pro).

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses side effect: 'writes a new handoff receipt via ai.handoff_receipts.create_receipt' and suggests subsequent action. Lacks details on persistence or visibility, but for a create tool this is sufficient.

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?

Description is concise with no redundant sentences. Clear structure: summary line, usage guidelines (when/when not), sibling contrast, and side effects. Every sentence adds value.

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?

Despite 11 parameters, the schema fully documents each. The description covers purpose, usage, side effects, and sibling differentiation. Output schema exists, so return values are documented. No gaps remain.

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 coverage is 100% with parameter descriptions that are self-explanatory (e.g., 'Comma-separated completed items'). The description does not add additional meaning or examples beyond the schema, so 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?

Description clearly states 'Create a handoff receipt when transitioning between agents (Pro).' It specifies the verb (create), resource (handoff receipt), and context (agent transition). Differentiates from siblings by naming delimit_session_handoff and delimit_handoff_acknowledge as alternatives to avoid.

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?

Explicitly provides 'When to use' (end of session or before passing work) and 'When NOT to use' (general summary or acknowledge), naming specific alternative tools. Also includes sibling contrast section that further clarifies scope differences.

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