Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Delimit Session Handoff

delimit_session_handoff

Capture a structured session handoff with summary, blockers, decisions, and changed files to preserve continuity across sessions and ensure the next revive restores this state.

Instructions

Save a session summary for cross-session continuity.

When to use: at the end of a productive session, to leave a structured record the next session can recover. When NOT to use: for richer cross-model state (use delimit_soul_capture, which auto-detects more) or single-line memory (delimit_memory_store).

Sibling contrast: delimit_soul_capture writes a richer "soul" with git state; this writes a structured handoff with explicit fields.

Side effects: writes a handoff record via ai.ledger_manager.session_handoff. Coerces list inputs from comma strings via _coerce_list_arg. LED-3731: also refreshes a lightweight pointer-soul for project_path (default = cwd) so the NEXT delimit_revive for that project returns THIS handoff's state rather than a stale older soul.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYes2-3 sentence summary of the session. Required.
ventureNoVenture context. Empty = auto-detect.
blockersNoWhat's blocked and why.
items_addedNoNewly added item ids as list or comma string.
project_pathNoProject path whose revive soul this handoff should refresh. Empty = auto-detect from cwd.
files_changedNoKey files that were modified.
key_decisionsNoKey decisions or consensus results.
items_completedNoCompleted ledger item ids (e.g. ["LED-164"]) as list or comma string.

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": "Project path whose revive soul this handoff should refresh. Empty = auto-detect from cwd.",
+  "type": "string"
+}
  2. Changed4 schema fields changedv4.7.9
    • changedInput schema / properties / items_added / description
      Previous value: -"List of newly added item IDs."New value: +"Newly added item ids as list or comma string."
    • changedInput schema / properties / items_completed / description
      Previous value: -"List of completed ledger item IDs (e.g. [\"LED-164\", \"LED-165\"])."New value: +"Completed ledger item ids (e.g. [\"LED-164\"]) as list or comma string."
    • changedInput schema / properties / summary / description
      Previous value: -"2-3 sentence summary of what happened this session."New value: +"2-3 sentence summary of the session. Required."
    • changedInput schema / properties / venture / description
      Previous value: -"Venture context. Auto-detects if empty."New value: +"Venture context. Empty = auto-detect."
  3. Addedv4.5.5

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by describing side effects: writes a handoff record via ai.ledger_manager.session_handoff, coerces list inputs from comma strings, and refreshes a pointer-soul for project_path which affects future delimit_revive behavior. This discloses meaningful state-changing behavior beyond what readOnlyHint/destructiveHint convey.

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 description is longer than average but logically structured with a lead sentence, usage guidance, sibling contrast, and side effects. The internal ticket reference (LED-3731) adds minor noise, but every major section earns its place and the core action is front-loaded.

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 an 8-parameter tool with an output schema, complete schema coverage, and clear annotations, this description covers the action, alternatives, side effects, and downstream behavioral implications. Nothing needed for correct invocation or sibling differentiation 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%, so detailed per-parameter semantics already exist in the schema. The description adds useful context about comma-string coercion and project_path default behavior, but these are also partially implied by the schema and do not fundamentally compensate for missing schema info.

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 states a specific action ('Save a session summary') with a clear resource and purpose (cross-session continuity). It also distinguishes the tool from siblings by explicitly contrasting it with delimit_soul_capture and delimit_memory_store.

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?

Provides explicit 'When to use' and 'When NOT to use' guidance, including named alternatives (delimit_soul_capture, delimit_memory_store) and the conditions that would select each. This gives the agent directly actionable routing information.

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