Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Delimit Session Handoff

delimit_session_handoff

Creates a structured handoff for session continuity, capturing summary, key decisions, completed items, and modified files for the next session.

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. Identifier/path fields retain legacy comma-list coercion. Prose decisions and blockers preserve commas in a plain string; native/JSON lists carry multiple entries. 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.7/5.0
Behavior5/5

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

The description discloses side effects: 'writes a handoff record via ai.ledger_manager.session_handoff' and 'refreshes a lightweight pointer-soul.' It also explains the legacy comma-list coercion behavior for certain fields. This transparency aligns with the annotations (readOnlyHint: false, destructiveHint: false) and there is no contradiction.

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 well-structured with labeled sections ('When to use', 'When NOT to use', 'Sibling contrast', 'Side effects') and is not excessively verbose. It includes some dense technical notes (e.g., about comma-list coercion and pointer-soul refresh) that are relevant but could be streamlined for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose, usage conditions, alternatives, side effects, and parameter clarifications. It does not mention the output schema, but that is not necessary for invocation. Given the tool's moderate complexity, the description provides sufficient context for an agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 8 parameters have descriptions in the schema, covering their meaning and defaults (e.g., venture: 'Empty = auto-detect'). The tool description adds context by explaining how list fields accept both comma strings and native arrays. While some descriptions are terse, the overall semantics are clear and the description supplements the schema effectively.

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 clearly states the tool's purpose: 'Save a session summary for cross-session continuity.' It uses a specific verb ('Save') and identifies the resource ('session summary'). It also distinguishes itself from sibling tools by explicitly contrasting with delimit_soul_capture and delimit_memory_store, so an agent can differentiate without inspecting schemas.

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?

The description provides explicit guidance on when to use ('at the end of a productive session') and when NOT to use it, naming alternative tools for richer state and single-line memory. This gives an agent clear decision criteria and prevents misuse.

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