Lists all Pan Docs chapters grouped by part, helping you locate a specific chapter's page name to pass to the page lookup tool.
List every Pan Docs chapter, grouped by part.
Use this to orient yourself in the book or to find the page name to pass to
pandocs_get_page. Returns chapter titles, page ids, URLs and section counts.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must carry the full burden. It does mention what the tool returns ('chapter titles, page ids, URLs and section counts') and implies it is read-only (listing chapters), but it does not explicitly address side effects, authentication requirements, or any limitations, leaving some transparency gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is succinct, using only two sentences. It front-loads the core function, then provides usage guidance and return information without any unnecessary verbosity. The structure is clear and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given there is no output schema, the description adequately explains what is returned. It covers the purpose, usage, and return payload. With no parameters and the tool's simple nature, the description provides all necessary context for an agent to correctly invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no properties, so schema description coverage is 100% (trivially). Since there are no parameters, there is nothing additional for the description to explain. Per the baseline rule for high coverage, this scores a 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'List every Pan Docs chapter, grouped by part.' It distinguishes itself from sibling tools by explaining it is used to orient in the book and to find page names for pandocs_get_page, making its unique role evident.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly tells when to use the tool: 'Use this to orient yourself in the book or to find the page name to pass to pandocs_get_page.' It does not explicitly state when not to use it or mention alternatives like pandocs_search, but the primary use case is well-defined and the context of sibling tools implies other functions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.