Skip to main content
Glama

Delimit Ledger Update

delimit_ledger_update

Update an existing ledger item's fields—status, priority, assignee, labels, or title—by passing only the values to change. Use it to modify item details without creating a new item or marking it done.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv4.7.9
    • changedInput schema / properties / assignee / description
      Previous value: -"Assign to a person or agent (e.g. \"founder\", \"claude\", \"codex\")."New value: +"Assign to person or agent (e.g. \"founder\", \"claude\")."
    • changedInput schema / properties / blocked_by / description
      Previous value: -"Item ID that blocks this item (e.g. \"LED-025\")."New value: +"Item id that blocks this one (e.g. \"LED-025\")."
    • changedInput schema / properties / blocks / description
      Previous value: -"Item ID that this item blocks (e.g. \"STR-005\")."New value: +"Item id that this one blocks (e.g. \"STR-005\")."
    • changedInput schema / properties / due_date / description
      Previous value: -"Due date in ISO format (e.g. \"2026-04-01\")."New value: +"ISO date string (e.g. \"2026-04-01\")."
    • changedInput schema / properties / item_id / description
      Previous value: -"The item ID (e.g. LED-001 or STR-001)."New value: +"Ledger item id, e.g. \"LED-001\" or \"STR-001\". Required."
    • changedInput schema / properties / labels / description
      Previous value: -"Labels/tags (e.g. [\"dashboard\", \"ux\"] or \"dashboard,ux\")."New value: +"Labels/tags as comma string or list."
    • changedInput schema / properties / note / description
      Previous value: -"Add a note/comment to the item."New value: +"Append a note/comment to the item."
    • changedInput schema / properties / priority / description
      Previous value: -"New priority - \"P0\", \"P1\", \"P2\"."New value: +"New priority — \"P0\", \"P1\", \"P2\"."
    • changedInput schema / properties / status / description
      Previous value: -"New status - \"open\", \"in_progress\", \"blocked\", \"done\"."New value: +"New status — \"open\", \"in_progress\", \"blocked\", \"done\"."
    • changedInput schema / properties / venture / description
      Previous value: -"Project name or path. Auto-detects if empty."New value: +"Project name/path. Empty = auto-detect."
    • changedInput schema / properties / worked_by / description
      Previous value: -"Which AI model is working on this. Auto-detected if empty."New value: +"AI model working on this. Empty = auto-detect."
  2. Addedv4.5.5

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses the key behavioral trait: 'writes to the ledger via ai.ledger_manager.' It also explains the label coercion behavior through _coerce_list_arg. This adds meaningful context beyond the annotations, which only say readOnlyHint=false and destructiveHint=false.

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 and well-organized with clear sections: purpose, when to use, when not to use, sibling contrast, and side effects. Every sentence contributes useful information without redundancy.

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 the rich 100%-covered input schema and the presence of an output schema, the description covers everything needed: purpose, selection criteria, alternatives, side effects, and partial-update semantics. No critical information is missing for correct invocation.

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?

Schema coverage is 100%, so the input schema already documents all 13 parameters. The description adds important usage semantics beyond the schema: 'Pass only the fields you want to change' clarifies partial-update behavior, and the label coercion note explains how the labels parameter is normalized.

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 specific verb and resource: 'Update any field on an existing ledger item.' It clearly distinguishes the tool from delimit_ledger_add and delimit_ledger_done, making its role as the general-purpose updater 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?

The description gives explicit when-to-use guidance ('to change state on a ledger item'), when-not-to-use guidance ('to create a new item... or to mark one done'), and names the exact sibling alternatives. This leaves no ambiguity about 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