Skip to main content
Glama

touhou_wiki_get_section

Fetch a single Touhou Wiki article section by numeric index or heading name to retrieve focused content without loading the full page.

Instructions

Fetch a single section of a Touhou Wiki article by numeric section index (e.g. "0" for Lead/Infobox, "1", "2") or by section heading name (e.g. "Personality", "Abilities").

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>",
      "section": "<section>"
    },
    "name": "touhou_wiki_get_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesArticle title (e.g. "Reimu Hakurei").
sectionYesNumeric section index ("0" for lead) or case-insensitive heading name.
max_charsNoMaximum cleaned content characters to return (500–24000, default 8000).
include_raw_wikitextNoInclude raw wikitext for the section (default false).

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 full burden. "Fetch" implies a read-only operation and the max_chars parameter hints at truncation of cleaned content, but the description says nothing about error behavior for invalid sections, caching, rate limits, or what the returned content looks like.

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 well-formed sentence with the resource and both identification modes front-loaded; no filler. It could be slightly tighter, but every clause carries information.

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 read-only, four-parameter tool with full schema coverage and no output schema, the description covers the essentials of what is fetched and how to address it. The main gap is the lack of guidance on discovering section indices or relating to sibling tools.

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 all four parameters are already documented in the schema. The description reinforces the section parameter with concrete examples ("0" for Lead/Infobox, "Personality", "Abilities") but adds no meaning beyond what the schema provides, so the 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?

States a specific verb ("Fetch") and resource ("a single section of a Touhou Wiki article") and explains the two ways to identify the section (numeric index or heading name). It implicitly distinguishes itself from whole-page and section-listing siblings by emphasizing "single section," though it never names them.

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 retrieving one section's content, but the description never says when to prefer it over touhou_wiki_get_page or how to obtain a valid index via touhou_wiki_get_sections. No exclusions or prerequisites are stated.

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