Skip to main content
Glama

touhou_wiki_get_sections

Retrieves an article's table of contents—section index numbers, hierarchy levels, titles, and anchors—without loading the full body, so you can locate and target specific sections before fetching content.

Instructions

Retrieve the Table of Contents (section index numbers, hierarchy levels, titles, and anchors) for a Touhou Wiki article without loading its full body.

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

Input Schema

NameRequiredDescriptionDefault
titleYesArticle title (e.g. "Reimu Hakurei", "Embodiment of Scarlet Devil").

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?

With no annotations supplied, the description carries the full burden. It discloses one meaningful behavioral trait — this is a lightweight read that avoids fetching the article body — but says nothing about error behavior for nonexistent or redirected titles, auth needs, or rate limits.

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?

One sentence, front-loaded with the action and payload, with the no-full-body constraint placed at the end. Nothing redundant or padded.

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 one-parameter read tool with no output schema, the description covers what is returned well enough to act on. The remaining gap is routing relative to the full-page and single-section siblings, which is not addressed.

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% and the single parameter is already documented with example article titles in the schema, so the description adds no syntax or format detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 ('Retrieve') and resource ('Table of Contents ... for a Touhou Wiki article') and even enumerates the returned fields (index numbers, hierarchy levels, titles, anchors). It also implicitly contrasts with full-page fetching via 'without loading its full body', though it does not name the sibling tool that does that.

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?

The phrase 'without loading its full body' implies the intended use case: cheaply inspect structure before choosing a section. However, there is no explicit when-to-use/when-not guidance and no named alternative such as a full-page or single-section fetch, so the agent must infer the routing.

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