Skip to main content
Glama

link

Create relationships between lore items or documents using mutual links, reading order, or replacement actions. Supports auto-classification of non-id values.

Instructions

link(a, b, action=) — connect two items (dc↔dc / lr↔lr / dc↔lr auto-detected, prefix matching OK). a/b may also be a file path or an existing title — non-id-shaped values are auto-classified (same as links= in add/edit). Undo (inverse) = unlink(a, b) — same arguments.

action has 3 modes (extends the member/config(action=) convention):

  • action='related' (default, same if omitted) → mutual link (symmetric). Same as link(a, b) — dc↔dc/lr↔lr/dc↔lr

  • action='flow' → not a mutual link but document order (a→b direction, doc↔doc only): read a, then b.

  • action='supersede' → "a is replaced by b" — a=old (dropped, head=False/dropped), b=target (alive, must be an existing item — none is created). lore↔lore or doc↔doc only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aNo
bNo
helpNo
actionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It explains symmetric linking, directional flow, and replacement semantics for supersede. It also describes auto-classification of non-id values and the undo behavior. No contradictions with annotations (none provided).

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?

The description is well-structured with bullet-like lines and front-loads the core function. It is somewhat lengthy but every sentence adds value. A slight reduction could improve conciseness, but it is not overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (multiple action modes, parameter auto-detection), the description covers most aspects. However, it lacks explanation of the 'help' parameter, default values, output format, and potential error conditions. The existing output schema mitigates some return value ambiguity.

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?

The schema has 0% description coverage, so the description must explain parameters. It describes 'a' and 'b' as items, file paths, or titles, and details the 'action' parameter's three modes. The 'help' parameter is not mentioned, but it is a minor omission.

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 tool's purpose: 'connect two items'. It specifies the types of items (dc↔lr, etc.) and mentions prefix matching and auto-detection. It distinguishes the tool from sibling 'unlink' by explicitly naming it as the inverse operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the three action modes (related, flow, supersede) and provides guidance on when to use each. It also notes that the default action is 'related' and that the inverse is 'unlink'. However, it does not compare to other sibling tools like 'add' or 'edit'.

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/linklore/linklore-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server