Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Delimit Handoff List

delimit_handoff_list
Read-onlyIdempotent

Retrieve pending session handoff receipts at startup to see what previous sessions left, or audit acknowledged handoffs.

Instructions

List session handoff receipts.

When to use: at session start to see what previous sessions left pending, or to audit acknowledged handoffs. When NOT to use: to create a handoff (use delimit_handoff_create) or acknowledge one (delimit_handoff_acknowledge).

Sibling contrast: delimit_handoff_create writes; delimit_handoff_acknowledge closes; this reads the receipt list.

Side effects: read-only. Calls ai.handoff_receipts.get_receipts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum receipts to return, 1-200. Default 50.
statusNo"pending" (default), "acknowledged", or "all".pending
project_pathNoOptional exact project namespace. Blank aggregates all namespaces.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed2 schema fields changedv4.13.2
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Maximum receipts to return, 1-200. Default 50.",
+  "type": "integer"
+}
    • addedInput schema / properties / project_path
      Added value: +{
+  "default": "",
+  "description": "Optional exact project namespace. Blank aggregates all namespaces.",
+  "type": "string"
+}
  2. Changed1 schema field changedv4.7.9
    • changedInput schema / properties / status / description
      Previous value: -"\"pending\" (unacknowledged), \"acknowledged\", or \"all\"."New value: +"\"pending\" (default), \"acknowledged\", or \"all\"."
  3. Addedv4.5.5

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds a clear 'Side effects: read-only' statement and names the underlying function call, which provides useful implementation context without contradicting the annotations.

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 compact and well-structured, with each section earning its place: purpose, usage, exclusions, sibling contrast, and side effects. Key information is front-loaded and scannable.

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?

For a read-only list tool with full schema coverage, an output schema, and clear sibling differentiation, the description covers when to use, when not to use, alternatives, side effects, and the backing implementation. Nothing material is missing.

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%, with each parameter already documented including defaults and allowed values. The description adds no extra parameter-level meaning, but the schema fully carries the burden, so the baseline 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?

The description opens with a specific verb and resource: 'List session handoff receipts.' It immediately distinguishes itself from sibling write/acknowledge tools, so an agent can tell exactly what this tool does and does not do.

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 provides explicit when-to-use scenarios ('at session start...', 'to audit acknowledged handoffs') and explicit when-not-to-use guidance with named alternatives (delimit_handoff_create, delimit_handoff_acknowledge). The sibling contrast makes routing unambiguous.

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