Skip to main content
Glama

touhou_wiki_search

Search Touhou Wiki by article title or full text to find characters, locations, spell cards, music, games, and lore, returning ranked results with URLs and clean snippets.

Instructions

Search en.touhouwiki.net across article titles (opensearch) and full article text (MediaWiki search). Returns ranked hits with URLs and clean text snippets.

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": {
      "query": "<query>"
    },
    "name": "touhou_wiki_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (1–20, default 8).
queryYesSearch query (character, location, spell card, music track, game, or lore topic).
include_subpagesNoWhether to include subpages containing "/" (default true).

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 burden. It does disclose the return shape (ranked hits with URLs and clean text snippets) and that two search backends are combined, which is genuinely useful, but it says nothing about rate limits, error behavior, or whether the two result sets are merged or interleaved.

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?

Two dense sentences with zero filler. The search scope is front-loaded and the return format follows immediately, so an agent gets both the what and the result shape at a glance.

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 low-risk read-only search tool with all three parameters documented and the return shape described in prose, the definition is nearly sufficient. The absence of an output schema is compensated by the 'ranked hits with URLs and clean text snippets' line; only pagination/rate behavior is left unstated.

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 description coverage is 100%, so limit, query, and include_subpages are already fully documented in the schema. The description adds no parameter-level detail beyond that baseline, such as how ranking differs between the title and full-text passes.

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 (Search) and resource (en.touhouwiki.net articles), and names the two mechanisms used: opensearch for titles and MediaWiki search for full text. This clearly separates it from the get_page/get_section siblings, which retrieve known pages rather than searching.

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 implied rather than stated: an agent can infer this is the tool for discovery when a page name is unknown, but there is no explicit when-to-use or when-not-to-use guidance, nor any mention of following up with touhou_wiki_get_page after finding a hit.

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