Skip to main content
Glama

get_backlinks

Find notes that link to a specified note through [[wikilink]], helping you see existing dependencies before adding new content.

Instructions

Which notes link to this one with a [[wikilink]]? Useful for seeing what already depends on a topic before you add to it.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it conveys that this is a lookup ('Which notes link to this one?') but never states read-only behavior, what happens if the path does not exist, or whether the result is a list. It is adequate for a simple read tool, but the behavioral surface is thin; the presence of an output schema covers return format.

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?

Two short sentences, front-loaded with the core question and followed by the motivating use case. Nothing is redundant, though the question phrasing is marginally less direct than a declarative statement of purpose.

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

Completeness4/5

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

For a one-parameter read-only lookup with an output schema, the definition supplies enough to call it correctly in most cases. The remaining gap is path format conventions, which is minor relative to the tool's simplicity.

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 coverage is 0% for the single 'path' parameter. The phrase 'this one' implies the path identifies a note, which is a modest semantic addition, but no path format (vault-relative, extension, case) is given, so the parameter remains underspecified in prose as well.

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 names a specific verb+resource: notes that link to a given note via [[wikilink]], which is a distinct concept from siblings like related_notes or query_notes. It is clear what is being fetched, though it does not explicitly contrast itself with any sibling tool.

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?

It offers one concrete scenario ('seeing what already depends on a topic before you add to it'), which implies when the tool is useful. There is no guidance on when not to use it or which sibling to prefer for related-but-different lookups.

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