Skip to main content
Glama

find_broken_links

Identify wiki notes that link to non-existent note IDs and list each source-to-broken-target pair for maintenance, returning a checkmark when no broken links exist.

Instructions

존재하지 않는 [[id]]를 참조하는 노트 찾기 (wiki 유지보수).

Returns: broken link 목록 (source → broken target). 없으면 ✅

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": "find_broken_links"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the burden: the word 'find' implies a safe read and the Returns block states the output shape (source → broken target, ✅ when none). However, it never explicitly states there are no side effects, what scope of the wiki is scanned, or whether the scan is expensive on large wikis — gaps that matter for a zero-annotation tool.

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 segments — purpose first, then a labeled Returns block — with no wasted words and the core rule front-loaded. The Returns detail slightly duplicates the output schema, but it is brief enough to earn its place.

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 zero-parameter, read-only diagnostic with an output schema already present, this is nearly complete: the definition explains what counts as broken and what the result looks like. Only the explicit read-only/no-side-effect statement and scan scope are missing, which is a minor gap at this complexity.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline of 4 applies. Nothing in the description contradicts or misdescribes the empty schema.

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 states a specific verb and resource plus the exact detection rule: find notes that reference a non-existent [[id]], tagged as wiki maintenance. That is far more precise than a name restatement. It does not name a sibling such as verify_citations or find_related, so an agent gets no explicit contrast, which keeps it at 4 rather than 5.

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?

The parenthetical '(wiki 유지보수)' implies the usage context: this is a wiki housekeeping/diagnostic check. There is no explicit when-to-use versus when-not, no alternative tool named, and no stated precondition (e.g., run after rename/delete), so guidance is implied rather than stated.

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