Skip to main content
Glama

Check links

wiki_check
Read-only

The links a wiki holds, in its pages and records, that point at nothing: each with why (no such wiki, page, or record), the page it most likely meant, and the pages and records that carry it. Give a page's path to check it and the pages beneath 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>",
      "org": "<org>"
    },
    "name": "wiki_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's path; the name and colon alone (general:) is the whole wiki.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), so the description's value is in disclosing the return shape: per broken link the failure reason, the most likely intended target, and the pages and records carrying the reference. It also discloses recursive scope over subpages, which is non-obvious. It does not discuss cost or volume limits on large wikis, keeping it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the output-shape detail leads. The first sentence is long and colon-heavy, packing four ideas into one clause, which slows parsing slightly, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing results and does so in concrete terms (reason, suggested replacement, carriers). For a two-parameter read tool whose annotations already cover safety, the remaining gaps (result size, pagination, what happens for a nonexistent wiki) are minor.

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 100%, so the baseline is 3, and the description earns extra credit by adding behavioral semantics to path that the schema lacks: the path selects a page and all pages beneath it, making the check recursive. It also reinforces that the wiki name comes from the path prefix rather than from org.

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 resource and condition: links held by a wiki, in its pages and records, "that point at nothing." Phrased as a noun clause rather than a verb, but an agent can still tell this audits for broken links, not the general link listing a sibling like wiki_links would give.

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 second sentence gives real scoping guidance: pass a page path to check that page and everything beneath it. It never states when to choose this over link-listing or resolution siblings, and gives no exclusions or preconditions beyond the implicit path requirement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources