Skip to main content
Glama

delimit_ledger_auto_cancel_stale

Archives open ledger items dormant beyond a stale-TTL threshold (default 60 days). Use as nightly automation; dry_run=True returns plan, False applies archive.

Instructions

Auto-archive open ledger items dormant past the stale-TTL threshold.

When to use: as nightly automation / scripted cleanup to retire items that have gone quiet past a strict threshold (default 60 days). When NOT to use: to merely surface stale candidates without applying (use delimit_ledger_groom which is propose-only and uses a softer 30-day default), to inspect ledger health (use delimit_ledger_health), or to auto-close items mirrored from external repos (delimit_ledger_auto_close_external).

Sibling contrast: delimit_ledger_groom proposes archives with a softer threshold and never applies; delimit_ledger_auto_close_external targets externally-mirrored items; delimit_ledger_bulk is the underlying bulk-action surface; this composes the stale-detector with bulk_action(archive) on a stricter dormancy threshold.

Side effects: with dry_run=False, archives matching items via bulk_action(archive). Items are never hard-deleted — the JSONL append-only log retains the full record. With dry_run=True (default), returns the plan only.

LED-1145 Phase 2 #4.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ventureNoProject name or path. Auto-detects if empty.
threshold_daysNodormancy threshold in days. 0 = read default (60 from STALE_TTL_DEFAULT_DAYS or DELIMIT_STALE_TTL_DAYS env). Pass an int to override.
dry_runNoTrue (default) returns the plan; False applies via bulk_action(archive).
max_itemsNocap items processed per call. When the candidate list exceeds this, response includes truncated=True so the caller can run again to drain.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Given no annotations, the description fully compensates by detailing side effects: with dry_run=False archives items via bulk_action(archive), never hard-deletes (JSONL log retains record), and dry_run=True returns plan only. This covers safety, idempotency, and data retention behavior.

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 clear sections and front-loaded purpose. While thorough, it is slightly longer than necessary; a bit more compaction could improve conciseness.

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?

Given 4 parameters, an output schema, and no annotations, the description covers usage, side effects, sibling contrasts, and default behaviors comprehensively. Nothing critical is missing for an automation tool.

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 schema already documents all 4 parameters. The description adds minimal extra value beyond the schema, mainly clarifying default threshold source and dry_run behavior. Baseline 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 clear verb+resource statement: 'Auto-archive open ledger items dormant past the stale-TTL threshold.' It then differentiates from siblings like delimit_ledger_groom, delimit_ledger_auto_close_external, and delimit_ledger_bulk, making the tool's specific role unmistakable.

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?

Explicit 'When to use' and 'When NOT to use' sections highlight appropriate scenarios, such as nightly automation, and warn against using it for inspection or external repo items. Sibling contrast further clarifies the distinction between propose-only, close-external, and raw bulk action tools.

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