Skip to main content
Glama
Sign In
vault-engine

vault-engine

by Bagas10k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vault_get_backlinks

Retrieve a note's inbound and outbound wikilinks and detect broken links in its vault graph, so you can inspect references and fix missing notes.

Instructions

[BACKLINK NAVIGATOR] Dapatkan seluruh catatan yang merujuk (inbound links) dan dirujuk oleh (outbound links) satu catatan tertentu. Juga mendeteksi apakah ada broken wikilink di dalam catatan tersebut.

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": {
      "note_stem": "<note_stem>"
    },
    "name": "vault_get_backlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_stemYes
vault_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description has to carry the full behavioral burden. It discloses the dual direction of results (inbound plus outbound) and the broken-wikilink scan, which is useful, but says nothing about read-only safety, behavior when note_stem doesn't resolve to a note, or how vault_path defaults are applied.

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 sentences, front-loaded with the core action, with no filler. The bracketed '[BACKLINK NAVIGATOR]' tag adds little, and the description is in Indonesian while the schema and tool name are English, a minor consistency cost.

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 shape needn't be explained, but for a two-parameter tool with no annotations and zero schema docs the description leaves the key calling details (stem format, vault_path fallback, missing-note behavior, sibling disambiguation) unaddressed.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters. The description adds no meaning: it never explains that note_stem is a filename without extension (as opposed to a path or title), nor what a null vault_path implies. The description fails to compensate for the coverage gap.

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 and resource: retrieve notes that link into (inbound) and out from (outbound) a given note, plus broken-wikilink detection. That is far more specific than the bare name, though it doesn't explicitly separate the tool from the sibling vault_find_broken_links, whose purpose it partially overlaps.

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 implied — call this when you need the link neighborhood of one note — but there is no explicit when-to-use or when-not-to-use statement, and no guidance on choosing between this and vault_find_broken_links for the broken-link portion. The agent must infer the routing.

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