memkin

Manage Links

manage_links

Add or remove graph links between pages to maintain relationships such as mentions, depends_on, or works_on. On error, search for missing page slugs before retrying.

Instructions

manage_links

Add or remove graph links between pages.

When to use: maintain relationships such as mentions, depends_on, or works_on. When NOT to use: tagging; use manage_tags. Returns: ok plus action/from/to. On error: search for missing page slugs before retrying.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "manage_links"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Target page slug.
`from`	Yes	Source page slug.
`type`	No	Relationship type, default `mentions`.
`action`	Yes	Whether to add or remove the link.
`context`	No	Short relationship context.
`provenance`	No	Optional SourceRef provenance object.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the write succeeded.
`to`	Yes	Target slug.
`from`	Yes	Source slug.
`action`	Yes	Performed link action.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations provided, but description discloses return format ('Returns: ok plus action/from/to') and error handling. Mutation is implied by 'Add or remove', with no contradictions.

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 very concise, uses headings and bullet points effectively, and front-loads the main action without unnecessary words.

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 6 parameters (3 required), output schema, and nested objects, the description covers purpose, usage, return value, and error handling comprehensively, leaving minimal gaps for agent understanding.

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%, but description adds value by listing example relationship types (mentions, depends_on, works_on) beyond the schema's generic 'Relationship type', and clarifies 'context' field as 'short relationship context'.

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 'Add or remove graph links between pages', which is a specific verb+resource. It also distinguishes from sibling 'manage_tags' by explicitly stating when not to use.

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 ('maintain relationships such as mentions, depends_on, or works_on') and when-not-to-use ('tagging; use manage_tags'), plus error guidance ('search for missing page slugs before retrying').

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