Skip to main content
Glama

delimit_ledger_update

Update any field on an existing ledger item, such as status, priority, assignee, or labels. Pass only the fields to change.

Instructions

Update any field on an existing ledger item.

When to use: to change state on a ledger item (status, priority, assignee, links, labels). Pass only the fields you want to change. When NOT to use: to create a new item (use delimit_ledger_add) or to mark one done (delimit_ledger_done is the convenience wrapper).

Sibling contrast: delimit_ledger_add creates; delimit_ledger_done closes; this is the general-purpose updater.

Side effects: writes to the ledger via ai.ledger_manager. Coerces string list inputs (labels) through _coerce_list_arg.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesLedger item id, e.g. "LED-001" or "STR-001". Required.
ventureNoProject name/path. Empty = auto-detect.
statusNoNew status — "open", "in_progress", "blocked", "done".
priorityNoNew priority — "P0", "P1", "P2".
titleNoNew title.
descriptionNoNew description.
noteNoAppend a note/comment to the item.
assigneeNoAssign to person or agent (e.g. "founder", "claude").
due_dateNoISO date string (e.g. "2026-04-01").
labelsNoLabels/tags as comma string or list.
blocked_byNoItem id that blocks this one (e.g. "LED-025").
blocksNoItem id that this one blocks (e.g. "STR-005").
worked_byNoAI model working on this. Empty = auto-detect.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses side effects (writes to ledger via ai.ledger_manager, coerces labels list via _coerce_list_arg). Could mention error handling or response format, but overall adequate.

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?

Description is front-loaded with core action, then organized into clear sections (when to use, when not, sibling contrast, side effects). Every sentence serves a purpose, with no wasted 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?

Given tool complexity (13 params, output schema exists), description covers purpose, usage, side effects, and differentiation. Lacks details on return values or error behavior, but output schema exists to cover returns. Good overall 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% with well-described parameters. Description adds value with the hint 'Pass only the fields you want to change', but does not substantially extend schema info. 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 clearly states the verb 'Update' and the resource 'existing ledger item', and distinguishes from siblings like delimit_ledger_add (create) and delimit_ledger_done (close). It specifies scope as 'any field' with examples, making purpose unambiguous.

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 specific alternatives (delimit_ledger_add, delimit_ledger_done). Also includes sibling contrast, 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