Skip to main content
Glama

delimit_ledger_link

Create typed relationships between ledger items to track dependencies, structure, and duplicates. Use blocks, parent/child, or duplicates links to organize project items.

Instructions

Create a typed relationship between two ledger items.

When to use: to track dependencies and structure (blocks, parent/child, duplicates) between ledger items. When NOT to use: to read existing links (use delimit_ledger_links) or update other fields (delimit_ledger_update).

Sibling contrast: delimit_ledger_links reads; delimit_ledger_update changes simple fields; this writes a relationship.

Side effects: writes the link via ai.ledger_manager.link_items. "blocks" / "blocked_by" auto-create the reverse direction so both items see the relationship.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_idYesSource item id (e.g. "LED-025"). Required.
to_idYesTarget item id (e.g. "STR-005"). Required.
link_typeNoOne of "blocks" (default), "blocked_by", "parent", "child", "relates_to", "duplicates".blocks
noteNoOptional note explaining the relationship.
ventureNoProject name/path. 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 the description carries the full burden. It discloses side effects: 'writes the link via ai.ledger_manager.link_items' and auto-creation of reverse direction for 'blocks'/'blocked_by'. Could mention confirmation or return value, but output schema exists.

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?

Every sentence is purposeful: main action, usage guidance, side effects. No redundant or missing information. Efficiently structured.

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 presence of an output schema and full parameter schema coverage, the description completes the picture with usage guidelines and side effects. No gaps.

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 description adds value with examples (e.g., 'LED-025'), clarification of link_type values, and auto-detection for venture. No contradictions or omissions.

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 states 'Create a typed relationship between two ledger items' and specifies link types like blocks, parent/child, duplicates. It clearly distinguishes from siblings (delimit_ledger_links reads, delimit_ledger_update changes fields).

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?

Explicitly provides 'When to use' and 'When NOT to use' sections with alternative tools. Also includes sibling contrast, making it easy for the agent to choose correctly.

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