Skip to main content
Glama

get_backlinks

Lists all notes that reference a given note through [[wikilinks]], helping you trace inbound links and understand connections in your Markdown memory.

Instructions

List the notes that link to the given note id via [[wikilinks]].

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": {
      "id": "<id>"
    },
    "name": "get_backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the semantics that matter most for correctness: the direction is inbound ('link to the given note'), and only [[wikilink]] relations count. It omits the return shape (ids vs. titles vs. full notes), ordering, and what happens if the id does not exist, which are meaningful gaps for a zero-annotation tool.

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?

A single tightly written sentence with the operation and the scoping qualifier front-loaded and no filler. Nothing in it is redundant with the schema or annotations.

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?

The tool is simple (one required string, no nesting), so the description does not need much. However, with no output schema and no annotations, it should say what comes back — a list of note ids, titles, or bodies — since that determines whether the caller must chain into read_note. That gap is the main incompleteness.

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 description coverage is 0%, so the single 'id' property is documented nowhere but the schema type. The description compensates by stating it is a note id ('the given note id'), which disambiguates it from a path, title, or alias. It does not say how to obtain that id, keeping it from a 5.

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?

The description gives a specific verb ('List') and resource ('the notes that link to the given note id'), plus the exact linking mechanism ('[[wikilinks]]'). That is enough to distinguish it from a plain list_notes or read_note call. It stops short of a 5 only because it never contrasts itself with those siblings by name.

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 'the given note id' signals you need an existing note and want inbound links. There is no explicit statement of when to prefer this over read_note or list_notes, and no exclusions (e.g. that forward links or unlinked mentions are not returned).

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