Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Delimit Handoff Acknowledge

delimit_handoff_acknowledge

Acknowledge a pending handoff receipt before starting work, marking it as acknowledged and closing the loop.

Instructions

Acknowledge a pending handoff receipt before starting work.

When to use: at session start when delimit_handoff_list shows a pending receipt — the receiving agent must acknowledge before starting work. When NOT to use: to create a handoff (use delimit_handoff_create) or list receipts (delimit_handoff_list).

Sibling contrast: delimit_handoff_create writes; delimit_handoff_list reads; this closes the loop on a specific receipt.

Side effects: writes an acknowledgement record via ai.handoff_receipts.acknowledge_receipt; flips the receipt status from pending to acknowledged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional notes from the receiving agent.
receipt_idNoReceipt id to acknowledge. Required (empty string returns an error payload).
project_pathNoOptional exact project namespace. Blank searches all namespaces; an explicit path never writes outside that namespace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed1 schema field changedv4.13.2
    • addedInput schema / properties / project_path
      Added value: +{
+  "default": "",
+  "description": "Optional exact project namespace. Blank searches all namespaces; an explicit path never writes outside that namespace.",
+  "type": "string"
+}
  2. Changed1 schema field changedv4.7.9
    • changedInput schema / properties / receipt_id / description
      Previous value: -"The receipt ID to acknowledge."New value: +"Receipt id to acknowledge. Required (empty string returns an error payload)."
  3. Addedv4.5.5

TDQS

A4.7/5.0
Behavior5/5

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

Discloses concrete side effects beyond the annotations: writes an acknowledgement record via ai.handoff_receipts.acknowledge_receipt and flips receipt status from pending to acknowledged. This adds meaningful behavioral context and does not contradict readOnlyHint=false or 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 purpose, usage, sibling contrast, and side effects. Every section earns its place, and the key operational guidance is front-loaded before the longer side-effect detail.

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?

Complete for a handoff-acknowledgement tool: it explains when to use it, when not to, how it differs from siblings, and what state changes it causes. Since an output schema exists, the description does not need to explain return values.

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 baseline is 3; the schema already documents notes, receipt_id, and project_path. The description reinforces that a specific receipt is targeted but does not add new parameter-level meaning beyond what is already in 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?

States a specific verb and resource: 'Acknowledge a pending handoff receipt before starting work.' It also distinguishes itself from sibling tools by noting delimit_handoff_create writes, delimit_handoff_list reads, and this tool 'closes the loop on a specific receipt.'

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 a when-to-use condition ('at session start when delimit_handoff_list shows a pending receipt') and a when-NOT-to-use section that names the alternatives (delimit_handoff_create and delimit_handoff_list). This fully routes an agent to the correct tool.

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