Skip to main content
Glama

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. Redirects are followed and reported in redirected_from, and in redirect_section when the alias points into a section; the extract still covers the whole article. 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.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesArticle 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. Special: and Media: titles, and interwiki links such as "wikt:cat", name no page.
languageNoWikipedia language edition code (default "en"). Examples: "fr", "de", "ja".en

Output Schema

NameRequiredDescriptionDefault
urlNoCanonical 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.
errorNoPresent when the call failed. Absent on success.
titleNoResolved article title (may differ from input for redirects).
noticeNoGuidance when the page has no summary extract, when the title redirects into a section (naming its section_index once the table of contents confirms it), or when the redirect could not be checked.
pageidNoWikipedia page ID. Absent when the API omits it.
extractNoPlain-text summary extract — a truncated fragment from the start of the lead section, not the whole lead. Superscripts and subscripts stay apart from the text beside them (10²³, H₂O), as wikipedia_get_article renders them. Call wikipedia_get_article with section_index 0 for the full lead.
languageNoLanguage edition queried.
latitudeNoWGS 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.
longitudeNoWGS 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_typeNoPage type from the Wikipedia REST API: "standard" (an article, including one whose lead yields no extract), "disambiguation" (a disambiguation page — call wikipedia_search_articles with a more specific query), "mainpage" (the edition's Main Page), or "no-extract" (a page outside the article namespace, such as a category, or with non-wikitext content).
descriptionNoShort description of the article subject.
revision_idNoID 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_modifiedNoISO 8601 timestamp of that revision, for dating the content.
thumbnail_urlNoURL of the article thumbnail image, if available.
wikibase_itemNoWikidata QID (e.g. "Q28865"). Use to chain into wikidata-mcp-server without a separate lookup.
redirected_fromNoOriginal alias followed to the resolved article. Absent when the title is not a redirect, or when the redirect could not be checked (a notice then says so).
redirect_sectionNoSection of the article the alias points into — its heading when the table of contents confirms it, otherwise the alias's raw fragment. The extract still summarizes the whole article; a notice gives the section_index to read when it is confirmed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / title / description
      Previous 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."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. Special: and Media: titles, and interwiki links such as \"wikt:cat\", name no page."
    • 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_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."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No Wikipedia article exists for the given title. `invalid_title`: The title can name no page: it contains characters MediaWiki forbids in a page name, is a Special: or Media: title in any edition's spelling, or is an interwiki link such as \"wikt:cat\". `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 / notice / description
      Previous value: -"Guidance when the existing page has no summary extract."New value: +"Guidance when the page has no summary extract, when the title redirects into a section (naming its section_index once the table of contents confirms it), or when the redirect could not be checked."
    • changedOutput schema / properties / page_type / description
      Previous value: -"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."New value: +"Page type from the Wikipedia REST API: \"standard\" (an article, including one whose lead yields no extract), \"disambiguation\" (a disambiguation page — call wikipedia_search_articles with a more specific query), \"mainpage\" (the edition's Main Page), or \"no-extract\" (a page outside the article namespace, such as a category, or with non-wikitext content)."
    • addedOutput schema / properties / redirect_section
      Added value: +{
      +  "description": "Section of the article the alias points into — its heading when the table of contents confirms it, otherwise the alias's raw fragment. The extract still summarizes the whole article; a notice gives the section_index to read when it is confirmed.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / redirected_from
      Added value: +{
      +  "description": "Original alias followed to the resolved article. Absent when the title is not a redirect, or when the redirect could not be checked (a notice then says so).",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Guidance when the existing page has no summary extract.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / properties / extract / description
      Previous 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."New value: +"Plain-text summary extract — a truncated fragment from the start of the lead section, not the whole lead. Superscripts and subscripts stay apart from the text beside them (10²³, H₂O), as wikipedia_get_article renders them. Call wikipedia_get_article with section_index 0 for the full lead."
  4. Changed5 schema fields changed
    • 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"
      +}
  5. Changed4 schema fields changed
    • 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."
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld, so the description carries real weight and does: it discloses that the extract is truncated (as little as a tenth of the lead), that redirects are followed and surfaced in redirected_from/redirect_section, and that the extract still covers the whole article. The disambiguation branch is a behavioral edge case an agent would otherwise misread as success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and no filler sentences, though it is a dense single block mixing return fields, redirect behavior, and sibling routing. The routing advice would read better pulled forward, but nothing is redundant.

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?

An output schema exists, yet the description still pre-frames the key return fields (wikibase_item, thumbnail, revision, coordinates) so the agent knows the payload shape before calling. Combined with redirect and disambiguation handling, nothing needed to invoke it correctly is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning about title resolution that the schema does not: redirects are followed, aliases pointing into a section are reported, and a disambiguation match is a signal to retry with a different query. That is genuine semantic value beyond the parameter definition.

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 and resource ("Fetch the short article summary") and frames the exact question it answers ("what is X?"). It explicitly contrasts itself with wikipedia_get_article and names the depth condition that selects the sibling, so an agent can differentiate without opening either schema.

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 routing rules for each branch: use wikipedia_get_article with section_index 0 for the full lead, wikipedia_search_articles with a more specific query when page_type is disambiguation, and pass lat/long to wikipedia_search_nearby. It also states a default preference ("Prefer this over wikipedia_get_article unless article depth is needed").

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.