Skip to main content
Glama

touhou_wiki_get_page

Fetch Touhou Wiki articles with structured Infobox fields, Japanese metadata, images, categories, section TOC, and cleaned text for quick reference and research.

Instructions

Fetch an article from en.touhouwiki.net with structured Infobox fields, Japanese kanji/romaji metadata, primary image URL, categories, section TOC, and cleaned article text.

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": {
      "title": "<title>"
    },
    "name": "touhou_wiki_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesArticle title or search term (e.g. "Reimu Hakurei", "Hakurei Shrine", "Spell card").
max_charsNoMaximum cleaned content characters to return (500–24000, default 6000).
resolve_imageNoResolve the infobox primary image direct URL and dimensions (default true).
include_raw_wikitextNoInclude raw MediaWiki wikitext alongside cleaned text (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 useful work by disclosing the shape of the response (structured infobox, metadata, cleaned text) and that raw wikitext is optional, which tells the agent this is a read operation with a normalized output. It says nothing about rate limits, caching, redirect/disambiguation handling, or error behavior for nonexistent pages, which are the remaining behavioral gaps for a network-backed fetch.

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?

A single front-loaded sentence with no filler; every clause names a distinct piece of returned data. It is dense but readable, and the resource is identified before the payload list. Slightly long as one unbroken sentence, 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 and no annotations, the description must describe the return value, and it does so concretely by enumerating infobox fields, metadata, image URL, categories, TOC, and text. For a 4-parameter read tool this is close to sufficient; only failure modes and title-resolution behavior are unaddressed.

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 a bump by tying return content to parameters: "cleaned article text" clarifies what max_chars bounds and what include_raw_wikitext adds alongside, and "primary image URL" clarifies what resolve_image produces. It does not restate the 500–24000 range or defaults, but the schema already does that.

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?

States a specific verb ("Fetch") and resource ("an article from en.touhouwiki.net") and enumerates the payload: infobox fields, kanji/romaji metadata, image URL, categories, TOC, cleaned text. That is far more specific than a bare name restatement. It stops short of explicitly distinguishing itself from siblings like touhou_wiki_get_section or touhou_wiki_search, so an agent must infer that this is the whole-article tool.

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 verb "Fetch an article" plus the schema hint that title accepts a search term suggests this is the entry point for full-article retrieval. There is no explicit when-to-use/when-not guidance, no mention of when to prefer touhou_wiki_get_section for a single section, and no statement about what happens on a missing or ambiguous title.

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