Skip to main content
Glama
Sign In
vault-engine

vault-engine

by Bagas10k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vault_find_broken_links

Detects broken wikilinks across an Obsidian vault by finding [[...]] references to notes or files that do not exist, so you can identify and fix missing links.

Instructions

[BROKEN LINK DETECTOR] Temukan seluruh tautan wikilink [[...]] yang putus di seluruh vault (merujuk ke berkas/catatan yang belum pernah dibuat).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vault_find_broken_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the scan scope ('seluruh vault') and defines 'broken' as links to files that were never created, which is genuine added context; however, it says nothing about cost/performance of a full-vault scan, permissions, or whether the operation is read-only, and it does not contradict anything since no annotations exist.

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?

One compact sentence with the label tag front-loaded and the scope/definition following; no wasted words. The bracketed tag is mild noise but does function as a quick category label.

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 values need not be explained, and the tool is a simple read with one optional parameter. Still, the description leaves the vault_path parameter and any cost considerations unaddressed, which is a meaningful gap for a whole-vault scan.

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% and the single parameter vault_path is never mentioned in the description, not even the fact that it is optional and defaults to null (presumably the active vault). With one undocumented parameter, 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 gives a specific verb ('Temukan' / find) and resource ('tautan wikilink [[...]] yang putus'), plus the scope ('seluruh vault') and a parenthetical definition of what counts as broken. An agent can distinguish it from vault_get_backlinks (which walks links from a note) and vault_lint_note without opening the schema, though no sibling is named explicitly.

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 parenthetical clarifies the failure mode, which suggests auditing/linting use, but there is no explicit when-to-use, when-not-to-use, or pointer to vault_get_backlinks / vault_lint_note as alternatives. The agent must infer the selection criteria.

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