wikipedia-mcp-server

Get Wikipedia Summary

wikipedia_get_summary

Read-only

Fetch the short article summary that answers "what is X?". The extract is a truncated fragment from the start of the lead section — usually a sentence or two, and as little as a tenth of the lead — alongside the Wikidata QID (wikibase_item) for cross-referencing with wikidata-mcp-server, a short description, a thumbnail URL, the canonical article URL, the revision the extract was read from, and, for a geotagged article, latitude and longitude that pass straight to wikipedia_search_nearby to answer "what else is notable near this". For the lead section in full, call wikipedia_get_article with section_index 0. Redirect pages are followed automatically. When page_type is "disambiguation", the title matched a disambiguation page — call wikipedia_search_articles with a more specific query to find the intended article. Prefer this over wikipedia_get_article unless article depth is needed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	Yes	Article title (URL-decoded), e.g. "Python (programming language)". A trailing #fragment is accepted and ignored; the characters < > [ ] { } and \| cannot appear in a Wikipedia page name.
`language`	No	Wikipedia language edition code (default "en"). Examples: "fr", "de", "ja".	en

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Canonical desktop URL of the article (e.g. "https://en.wikipedia.org/wiki/Eiffel_Tower"), for citing the page rather than composing a URL from the title.
`error`	No	Present when the call failed. Absent on success.
`title`	No	Resolved article title (may differ from input for redirects).
`pageid`	No	Wikipedia page ID. Absent when the API omits it.
`extract`	No	Plain-text summary extract — a truncated fragment from the start of the lead section, not the whole lead. Call wikipedia_get_article with section_index 0 for the full lead.
`language`	No	Language edition queried.
`latitude`	No	WGS 84 latitude of the article subject in decimal degrees. Pass with longitude to wikipedia_search_nearby, whose inputs carry these names, to find other notable articles around the same point. Absent for an article that is not geotagged.
`longitude`	No	WGS 84 longitude of the article subject in decimal degrees. Pass with latitude to wikipedia_search_nearby, whose inputs carry these names, to find other notable articles around the same point. Absent for an article that is not geotagged.
`page_type`	No	Page type from the Wikipedia REST API. Common values: "standard" (regular article), "disambiguation" (disambiguation page), "no-extract" (article with no extract). When "disambiguation", call wikipedia_search_articles with a more specific query.
`description`	No	Short description of the article subject.
`revision_id`	No	ID of the revision the extract was read from. "https://<edition>.wikipedia.org/w/index.php?oldid=<revision_id>" is a permanent link to exactly that version.
`last_modified`	No	ISO 8601 timestamp of that revision, for dating the content.
`thumbnail_url`	No	URL of the article thumbnail image, if available.
`wikibase_item`	No	Wikidata QID (e.g. "Q28865"). Use to chain into wikidata-mcp-server without a separate lookup.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 17, 2026

addedOutput schema / properties / last_modified

Added value: +{
+  "description": "ISO 8601 timestamp of that revision, for dating the content.",
+  "type": "string"
+}

addedOutput schema / properties / latitude

Added value: +{
+  "description": "WGS 84 latitude of the article subject in decimal degrees. Pass with longitude to wikipedia_search_nearby, whose inputs carry these names, to find other notable articles around the same point. Absent for an article that is not geotagged.",
+  "type": "number"
+}

addedOutput schema / properties / longitude

Added value: +{
+  "description": "WGS 84 longitude of the article subject in decimal degrees. Pass with latitude to wikipedia_search_nearby, whose inputs carry these names, to find other notable articles around the same point. Absent for an article that is not geotagged.",
+  "type": "number"
+}

addedOutput schema / properties / revision_id

Added value: +{
+  "description": "ID of the revision the extract was read from. \"https://<edition>.wikipedia.org/w/index.php?oldid=<revision_id>\" is a permanent link to exactly that version.",
+  "type": "string"
+}

addedOutput schema / properties / url

Added value: +{
+  "description": "Canonical desktop URL of the article (e.g. \"https://en.wikipedia.org/wiki/Eiffel_Tower\"), for citing the page rather than composing a URL from the title.",
+  "type": "string"
+}

Changed4 schema fields changedSep 17, 2026

changedInput schema / properties / title / description

Previous value: -"Article title (URL-decoded), e.g. \"Python (programming language)\"."New value: +"Article title (URL-decoded), e.g. \"Python (programming language)\". A trailing #fragment is accepted and ignored; the characters < > [ ] { } and | cannot appear in a Wikipedia page name."

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No Wikipedia article exists for the given title. `invalid_language`: The language is not a valid BCP 47 code, or names a Wikipedia edition that does not exist. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No Wikipedia article exists for the given title. `invalid_title`: The title contains characters MediaWiki cannot name a page with. `invalid_language`: The language is not a valid BCP 47 code, or names a Wikipedia edition that does not exist. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "not_found",
-  "invalid_language"
-]New value: +[
+  "not_found",
+  "invalid_title",
+  "invalid_language"
+]

changedOutput schema / properties / extract / description

Previous value: -"Plain-text lead-section extract."New value: +"Plain-text summary extract — a truncated fragment from the start of the lead section, not the whole lead. Call wikipedia_get_article with section_index 0 for the full lead."

First observedSep 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial behavior beyond the readOnlyHint/openWorldHint annotations: extract is a truncated fragment (as little as a tenth of the lead), redirects are followed automatically, and disambiguation page_type handling is explained. This gives the agent operational expectations not present in structured data.

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?

Every sentence earns its place: primary purpose first, then output-content detail, then sibling routing. The flow is logical and free of filler; even the longer sentence about returned fields packs necessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter tool with a rich output schema, the description covers all an agent needs: what the extract is, redirect behavior, disambiguation handling, the full-lead alternative, and preference over siblings. Nothing required for correct invocation is missing.

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 both parameters (title, language) are already fully described in the input schema. The description adds contextual usage (e.g., redirects, page_type) but no new parameter-level semantics, so the baseline of 3 applies.

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?

States a specific verb ('Fetch'), resource ('short article summary'), and purpose ('what is X?'). Explicitly distinguishes this from wikipedia_get_article, wikipedia_search_articles, and wikipedia_search_nearby, so an agent can tell them apart immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use vs alternatives: 'For the lead section in full, call wikipedia_get_article with section_index 0', 'When page_type is disambiguation... call wikipedia_search_articles', and 'Prefer this over wikipedia_get_article unless article depth is needed'. Also notes lat/long feeds wikipedia_search_nearby. Nothing is left to inference.

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

All wikipedia-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.