Skip to main content
Glama

touhou_wiki_list_subpages

List subpages under a Touhou Wiki article prefix, such as character or game pages, to browse related topics and discover linked entries. Set an optional limit to control how many results return.

Instructions

List subpages under a Touhou Wiki article prefix (e.g. "Perfect Memento in Strict Sense", "Embodiment of Scarlet Devil", "Forbidden Scrollery").

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum subpages to return (1–100, default 30).
titleYesParent article title whose subpages ("<Title>/...") should be listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 disclosure burden. 'List' implies a read-only operation and the prefix semantics ('<Title>/...') are conveyed via the schema, but the description never states what is returned, whether listing is flat or recursive, how results are ordered, or what happens if the title has no subpages.

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?

A single front-loaded sentence with the core operation first and illustrative examples after. No redundant or filler wording.

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

Completeness3/5

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

The tool is simple (two flat parameters, no output schema), and the description covers the core semantics. However, with no output schema and no annotations, leaving the return shape and listing behavior unexplained is a real gap for an agent deciding how to consume the result.

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%, including the 1-100 range and default of 30 for limit, so the schema does the heavy lifting. The description adds example values that clarify what a valid title looks like on this wiki, but nothing about limit behavior beyond the schema.

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 and resource ('List subpages under a Touhou Wiki article prefix') and grounds it with three concrete example titles, so an agent immediately knows the operation. It does not explicitly contrast with siblings like touhou_wiki_get_page or touhou_wiki_list_category, though 'subpages under a prefix' is naturally distinguishable.

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: an agent can infer this is the tool for enumerating a page's subpages rather than fetching page content. There is no statement of when to prefer it over a sibling, no prerequisites, and no exclusions.

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