Skip to main content
Glama

What links here

wiki_links
Read-only

What links to a page, or with key to one of its records: the pages and records that carry a wikilink to it, from its own wiki and from the organization's other wikis you may read. A linking record comes with its value.

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_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoA record of the page, by key; without it, the page itself.
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 dot-separated path (general:docs.deploy).
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this as a safe, non-destructive, closed-world read, so the bar is lower. The description still adds meaningful context: results span the page's own wiki plus other organization wikis the caller can read, and 'A linking record comes with its value' hints at the returned payload. It does not cover ordering or how the limit truncates results.

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 question 'What links to a page,' with no filler. The trailing clause 'A linking record comes with its value' is slightly cryptic but is the only statement about return contents, so it earns 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?

With no output schema, the description must hint at what comes back, and it does so at a high level plus the cross-wiki scope. For a four-parameter read-only lookup with 75% schema coverage, the remaining gaps (result ordering, pagination behavior under limit) are minor.

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

Parameters3/5

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

Schema coverage is 75%, so the baseline is 3. The description's handling of 'key' ('or with key to one of its records') largely restates the schema's own 'A record of the page, by key; without it, the page itself,' and it says nothing extra about org, path syntax, or the limit parameter.

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 the exact resource being returned: pages and records that carry a wikilink to a given page, and it extends the scope to 'the organization's other wikis you may read.' That is a specific backlinks query an agent can distinguish from a fetch (wiki_get/wiki_read) or a text search. It stops short of naming a sibling tool as the alternative, so a 4 rather than a 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 description implies the use case (find inbound references to a page) and clarifies the fork between page-level and record-level lookup via 'key.' However, it never states when to prefer this over wiki_search or wiki_get, nor any exclusions or prerequisites beyond the vague permission qualifier 'wikis you may read.'

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