worldanvil-mcp-server

Find references (backlinks)

find_references

Find all articles, secrets, and notes that link to a specific article using its UUID, preventing false positives. Useful for locating mentions or verifying impact before deletion.

Instructions

Find every article, secret or note that LINKS TO a given article. World Anvil stores links as @Title mentions, so this searches cached text for the target's uuid — exact backlinks, no false positives from name coincidences. Use it for questions like 'where is this NPC mentioned?' or before deleting an article. Self-refreshing cache; first call on a world builds it (can take a minute).

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": {
      "world_id": "<world_id>",
      "article_id": "<article_id>"
    },
    "name": "find_references"
  }
}

Input Schema

Name	Required	Description	Default
`world_id`	Yes	UUID of the world
`article_id`	Yes	UUID of the target article (find it via search_articles/search_content)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden. It discloses that the search is on cached text, uses exact UUID matching (no false positives), and that the first call builds the cache which can take a minute. This is substantial behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three sentences pack the essential information: purpose, mechanism, use cases, and a performance caveat. The most important fact is front-loaded, and every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what the tool does, how it operates, when to use it, and a key cache performance characteristic. Given the absence of annotations and output schema, this is sufficient for an agent to select and invoke the tool correctly.

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 100%, so the schema already fully documents both required parameters. The description does not add parameter-specific detail beyond the schema, so the baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description leads with a specific verb+resource: 'Find every article, secret or note that LINKS TO a given article.' It further distinguishes from sibling search tools by emphasizing exact UUID-based matching for backlinks, with no false positives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear use cases: 'where is this NPC mentioned?' or 'before deleting an article.' This gives an agent explicit context for when to use the tool, though it does not explicitly name alternative tools or exclusions.

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

Deploy Server