Skip to main content
Glama

Link two notes

link_notes
Idempotent

Link two existing notes by path or title within a memory map to connect related Markdown notes for later recall.

Instructions

Link two existing notes (paths or titles) so they're connected in the user's memory map.

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": {
      "from_note": "<from_note>",
      "to_note": "<to_note>"
    },
    "name": "link_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_noteYes
from_noteYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent, non-open-world mutation, so the safety profile is covered. The description adds the meaningful outcome that the two notes become 'connected in the user's memory map,' but says nothing about directionality, duplicate links, or what occurs if an identifier fails to resolve.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity comes at the cost of the unresolved gaps noted above.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. For a two-parameter linking mutation the remaining omissions are moderate: edge direction and failure behavior when a note cannot be found are left to inference.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate, and it partly does by stating that parameters accept either paths or titles. However, the essential semantic question for two params named from_note/to_note — whether the link is directed or symmetric — goes unanswered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Link two existing notes') and clarifies the accepted identifier forms ('paths or titles'). It does not differentiate itself from siblings like read_note or search_memory, but the action is unambiguous on its own.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'existing notes' signals a prerequisite that both notes must already exist before linking. There is no explicit when-to-use, when-not, or pointer to an alternative tool for cases where notes are missing or merely need reading.

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