Wikipedia MCP Server

wikipedia_get_article

Read-onlyIdempotent

Retrieve the full text and structure of a Wikipedia article by providing its title.

Instructions

Get the full content of a Wikipedia article.

Returns a dictionary containing article details or an error message if retrieval fails.

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": "wikipedia_get_article"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes

Output Schema

Name	Required	Description	Default
`title`	Yes
`exists`	Yes
`pageid`	No
`summary`	No
`text`	No
`url`	No
`sections`	No
`categories`	No
`links`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.1May 7, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds value by specifying the return type (dictionary) and error handling (error message if retrieval fails), which is useful context beyond what annotations provide.

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?

Two sentences, no redundant information, and the main purpose is front-loaded. Every word earns its place.

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?

Given the simple parameter set and strong annotations, the description is largely sufficient. It covers the primary outcome and failure mode. An output schema exists, so detailed return value documentation is unnecessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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 elaborate on the title parameter. While the parameter name is self-explanatory, the description fails to add meaning about formatting, disambiguation, or other nuances, leaving the agent to infer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves the full content of a Wikipedia article, using a specific verb and resource. It distinguishes from sibling tools like get_summary or 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.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool should be used when full article content is needed, but it does not explicitly mention alternatives or exclusion criteria. The presence of multiple similar sibling tools (e.g., get_article, get_summary) makes this a missed opportunity for clearer guidance.

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