Skip to main content
Glama
markdown-memory-mcp

markdown-memory-mcp

by amercans

backlinks

Find every note and index file linking to a given note via [[wikilink]] or Markdown link. Returns name, path, and line for each backlink.

Instructions

List the notes and index files that link to a note, by [[wikilink]] or Markdown link.

Args: name: The note's file name without .md, or its frontmatter name.

Returns a list of {name, path, line}. Empty if nothing links 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": {
      "name": "<name>"
    },
    "name": "backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the match semantics (both wikilink and Markdown link forms, index files included) plus the empty-result behavior. It omits ordering, cost, and whether index files are distinguished in output, so it stops short of a 5.

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?

Front-loaded purpose sentence followed by a tight Args and Returns block, with every line carrying information an agent needs. No filler or repetition.

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 single-parameter read tool this is complete: input form, matching rules, and result shape are all covered. Return values are also given even though an output schema exists, which is harmless redundancy rather than a gap.

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 0%, so the description must compensate, and it does: it explains that 'name' is the file name without the .md extension or the frontmatter 'name', which is a non-obvious dual-form input the schema alone does not convey. Ambiguity handling when both forms match is unaddressed.

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 states a specific verb ('List') and resource ('the notes and index files that link to a note'), and narrows the scope to inbound [[wikilink]] and Markdown links, including index files. That level of specificity makes it clearly distinct from read_note and search_notes without naming them.

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 by the purpose: an agent can infer 'use this to find inbound links,' but there is no explicit when-to-use, when-not-to-use, or statement about when search_notes would be preferable. It is adequate but leaves routing entirely to inference.

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

Deploy Server

Other Tools