wiki_get_page_categoriesRetrieve the categories a WikiPeatia page belongs to by providing its title. Use this to understand how a page is classified within the wiki.
Show which categories a page belongs to.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Page title |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden, but 'Show' does convey a read-only, non-destructive lookup and an output schema exists to define the return shape. It says nothing about behavior for missing pages, redirects, or result limits, which is a real gap for a tool with zero annotation coverage.
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?
One short, front-loaded sentence with zero filler. Every word earns its place.
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?
For a single-parameter read tool with an output schema, the definition covers the essentials and the return shape is delegated correctly. Minor gaps remain around edge-case behavior, but nothing critical to invoking it correctly is missing.
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?
Schema description coverage is 100% with a single 'title' parameter, so the schema already documents the input fully. The description adds no format hints (e.g., namespace prefixes, case sensitivity) beyond what the schema states, which is the expected baseline.
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?
States a specific verb ('Show') and resource ('categories a page belongs to'), and the per-page scoping implicitly separates it from siblings like wiki_list_categories (all categories) and wiki_get_category_members (reverse direction). It stops short of naming those siblings, so an agent must infer the distinction.
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?
There is no when-to-use guidance, no prerequisites, and no mention of alternative tools for related lookups. The agent must derive usage purely from the one-line purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.