Retrieve the complete content of a Wikipedia article by providing its title.
Get the full content of a Wikipedia article.
Returns a dictionary containing article details or an error message if retrieval fails.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| exists | Yes | ||
| pageid | No | ||
| summary | No | ||
| text | No | ||
| url | No | ||
| sections | No | ||
| categories | No | ||
| links | No | ||
| error | No |
Changes observed during successful MCP inspections.
v2.0.1v1.5.8v1.0.0Input schema / properties / title / titleRemoved value: -"Title"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. The description adds that it returns a dictionary or an error message on failure, which provides some behavioral context beyond annotations, but does not disclose additional details like rate limits or response structure.
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 two concise sentences, front-loaded with the primary purpose and no redundant information. Every sentence contributes to understanding the tool's function.
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?
The tool is simple with one parameter and an output schema, and annotations are comprehensive. However, given the many sibling tools, the description could be more complete by noting the scope (e.g., full content vs. summary) and any prerequisites. It is adequate but under-specified for the broader context.
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 0%, and the description does not explain the 'title' parameter beyond the tool's name. Since there is only one parameter, the description should compensate but does not, leaving the parameter semantics largely undefined.
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 'Get the full content of a Wikipedia article' with a specific verb and resource. It distinguishes from sibling tools like get_summary and get_sections by emphasizing 'full content'.
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?
Usage is implied: this tool is for fetching full article content. However, it does not explicitly mention alternatives or when to prefer other tools like get_summary or get_sections, so guidance is limited.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.