Skip to main content
Glama

delimit_ledger_bulk

Apply a single action to multiple ledger items in one call. Use after grooming to update statuses, priorities, or tags across a batch.

Instructions

Apply one action to many ledger items in a single call (LED-1145 Phase 1 PR-B).

When to use: after delimit_ledger_groom or another tool surfaces a list of item ids that should all receive the same change. When NOT to use: for a single item (use delimit_ledger_update or delimit_ledger_done).

Sibling contrast: delimit_ledger_update is one item; delimit_ledger_groom proposes; this applies bulk.

Side effects: when dry_run=False, writes status/priority/tag changes via the ledger manager. Per-item failures don't block the batch. Default dry_run=True returns what would change without writing — callers MUST explicitly pass dry_run=False to apply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idsYescomma-separated LED ids (e.g. "LED-915,LED-916,LED-918") or a JSON array of strings.
actionYesone of the actions above.
dry_runNoTrue (default) returns `would_change`; False applies and returns `changed`.
noteNooptional note attached to every successful update event.
new_statusNorequired when action="set_status".
new_priorityNorequired when action="set_priority".
tagNorequired when action="add_tag".
ventureNoproject name or path. Auto-detects if empty.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Despite no annotations, the description thoroughly explains side effects: writes status/priority/tag changes when dry_run=False, per-item failures don't block batch, default dry_run=True returns would_change, and callers must explicitly pass dry_run=False to apply.

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, well-structured with clear sections (When to use, When NOT, Sibling contrast, Side effects), and front-loads the core purpose without unnecessary words.

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?

Covers usage, dry_run behavior, batch resilience, and output format (would_change vs changed). Minor gap: the 'action' parameter values are referenced as 'the actions above' but no list is provided, slightly reducing completeness.

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 coverage is 100%, so parameters are already well-documented in the schema. The description adds little per-parameter detail beyond reinforcing dry_run and action semantics, warranting the baseline score.

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 verb 'Apply', the resource 'ledger items', and the scope 'bulk', distinguishing it from siblings like delimit_ledger_update (single item) and delimit_ledger_groom (proposes).

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, with alternatives named (delimit_ledger_update, delimit_ledger_done), providing clear context for tool selection.

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