Skip to main content
Glama

touhou_wiki_list_category

Lists pages or subcategories within a Touhou Wiki category and supports pagination, so you can browse category members and continue through results.

Instructions

List pages or subcategories in a Touhou Wiki Category (e.g. "Category:Characters", "Category:Locations", "Category:Official Games"), with pagination support.

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": {
      "category": "<category>"
    },
    "name": "touhou_wiki_list_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoNamespace filter: "articles" (ns=0, default), "subcategories" (ns=14), or "all".
limitNoMaximum members per page (1–200, default 50).
categoryYesCategory name with or without "Category:" prefix (e.g. "Locations" or "Category:Characters").
continue_tokenNoPagination token from a previous call (`next_continue_token`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 of disclosure. It does add useful behavioral context beyond the schema by flagging pagination support and framing the operation as a listing/browse. It does not say whether this is a read-only operation, whether results are ordered or how many namespaces are traversed when a category mixes pages and subcategories. For an unannotated tool it should state more, but the pagination note is real added value.

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 the verb and resource stated first, followed by examples and then the pagination note. Nothing is redundant or padded, and the parenthetical examples earn their place by showing the accepted naming format. Minor cost: the example list is somewhat long relative to the small amount of other content.

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?

For a 4-parameter listing tool with no annotations and no output schema, the description covers the core purpose and notes pagination, which is the main thing an agent needs to know about the call pattern. It leaves the return shape undocumented, does not explain how continue_token relates to a follow-up call, and does not clarify what the "all" namespace filter yields. Adequate but not complete for an unannotated tool.

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 per-parameter descriptions for type, limit, category, and continue_token, so the schema already does the heavy lifting. The description reinforces the category argument with example names ("Category:Characters", "Category:Locations"), but that duplicates the schema's own example. It adds no semantics for the enum, limit bounds, or token reuse beyond what the schema states, so baseline 3 applies.

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 uses a specific verb ("List") against a specific resource (pages or subcategories in a Touhou Wiki Category) and illustrates it with concrete category examples. It is clearly distinguishable from siblings like touhou_wiki_get_page or touhou_wiki_search, which fetch page content or perform text search rather than enumerate category membership. It stops short of naming those siblings explicitly, so it is clear but not fully differentiated by comparison.

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: the agent can infer this is the tool for browsing category membership, and the examples hint at namespace choices. However, there is no explicit when-to-use vs when-to-use-an-alternative guidance (e.g. when to prefer touhou_wiki_search over browsing a category), and no prerequisites are mentioned. Adequate but with clear gaps.

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