Skip to main content
Glama

Delimit Ledger Update

delimit_ledger_update

Update any field on an existing ledger item, including status, priority, assignee, labels, and more. Pass only the fields you want to change; use separate tools to create or close items.

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. LED-5658 review v2: a venture that resolves to UNKNOWN — no recognized slug AND no real project directory behind it (auto-detect, an empty venture, can never be unknown) — is rejected BEFORE any lookup or write, with {"error", "unknown_venture", "known_ventures"} and, when item_id is found to actually exist in some other real registered venture (read-only check, never a write), item_found_in naming it. Every other case — auto-detect, a recognized venture, or an explicit path to a real (even if unregistered) project — is unchanged: it keeps the existing cross-venture fallback search, and the response carries venture_fallback: true when that fallback is what located the item.

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").
evidenceNoOptional evidence object {class, kind, ref, observed_at, observed_by} (LED-5321 M4). Dict or JSON string.
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.
review_diff_pathNoOptional diff file path the transcript must bind to.
review_diff_textNoOptional inline diff text the transcript must bind to.
review_transcriptNoOptional transcript path for independently_reviewed binding.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.19.1
    • addedInput schema / properties / evidence
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional evidence object {class, kind, ref, observed_at, observed_by} (LED-5321 M4). Dict or JSON string."
      +}
    • addedInput schema / properties / review_diff_path
      Added value: +{
      +  "default": "",
      +  "description": "Optional diff file path the transcript must bind to.",
      +  "type": "string"
      +}
    • addedInput schema / properties / review_diff_text
      Added value: +{
      +  "default": "",
      +  "description": "Optional inline diff text the transcript must bind to.",
      +  "type": "string"
      +}
    • addedInput schema / properties / review_transcript
      Added value: +{
      +  "default": "",
      +  "description": "Optional transcript path for independently_reviewed binding.",
      +  "type": "string"
      +}
  2. 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."
  3. Addedv4.5.5

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, so the description adds substantial behavioral detail: writes to the ledger via ai.ledger_manager, label coercion through _coerce_list_arg, and precise unknown-venture rejection behavior including error keys, item_found_in and venture_fallback semantics. No contradiction with annotations.

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?

Cleanly structured with labeled sections and front-loaded purpose. The side-effects paragraph is dense and somewhat overlong, but it earns its place by documenting an important rejection path that is otherwise invisible to the agent.

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?

For a complex 17-parameter mutation tool, the description covers selection, invocation, side effects, and edge cases thoroughly. Output schema exists, so the lack of return-value prose is not a gap.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds non-derivable parameter behavior: partial-update semantics, label list coercion, and the venture edge-case resolution rules. This meaningfully goes beyond the baseline for fully documented schemas.

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?

States a specific verb and resource ('Update any field on an existing ledger item') and immediately distinguishes itself from delimit_ledger_add and delimit_ledger_done. The sibling contrast makes it unmistakably the general-purpose updater.

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?

Provides explicit when-to-use and when-not-to-use guidance, names the exact alternates (delimit_ledger_add for creation, delimit_ledger_done for closing), and gives a clear operational rule: pass only the fields to change.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools