Skip to main content
Glama

Documents linking here

ragdown_backlinks
Read-only

Finds documents that link to a specified Markdown file via wikilink, alias, or relative link and returns the linking lines, helping you identify dependencies before changing or superseding it.

Instructions

The documents that link to a document — by [[wikilink]], alias, or relative Markdown link — each with the lines the links are on. Use it to find what depends on or refers to a document, e.g. before changing or superseding 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": "ragdown_backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath of the document relative to the documents root

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv5.16.0
    • changedInput schema / properties / path / description
      Previous value: -"Path of the note relative to the notes root"New value: +"Path of the document relative to the documents root"
  3. Addedv5.9.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral detail beyond that by enumerating which link syntaxes are recognized (implicitly, which are not) and that results carry line numbers. It stops short of describing ordering, deduplication, or whether the search recurses across the vault.

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?

Two sentences, front-loaded with the definition and followed by the use case; every clause carries information (link forms, per-link line detail, motivating scenario) with no filler.

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?

For a one-parameter read-only lookup with no output schema, the definition is sufficient: it says what is searched, which link types count, what each result includes, and why an agent would call it. Nothing needed to invoke it correctly is missing.

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?

With a single required parameter and 100% schema description coverage, the schema already explains that path is relative to the documents root. The description adds no path formatting, aliasing, or resolution nuance beyond that, so the baseline applies.

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 names a specific resource (the documents that link to a document) and enumerates the exact link forms counted — [[wikilink]], alias, and relative Markdown link — plus what is returned per link. That verb/resource/scope precision lets an agent distinguish it from one-directional reads like ragdown_read_doc or ragdown_context.

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?

It states a clear situation for use: finding what depends on or refers to a document, with a concrete motivating case (before changing or superseding it). It does not explicitly say when not to use it or name an outgoing-links/traversal alternative, which keeps it below a 5.

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