Skip to main content
Glama

Wikipedia Summary API - article summary, image, coordinates in any language

wikipedia_summary
Read-onlyIdempotent

Get the lead summary of a Wikipedia article in any language edition: title, short description, plain-text extract, thumbnail and original image, coordinates, Wikidata id, last edit time and page link. Fuzzy title search. Attribution (CC BY-SA 4.0) included. ~0.5 s. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/wikipedia-summary.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "Eiffel Tower",
      "language": "en"
    },
    "name": "wikipedia_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoArticle title or search words, e.g. Varna
languageNoWikipedia language code, default en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnly/openWorld/idempotent) by disclosing latency (~0.5 s), free quota (25 calls/day per IP), paid rate ($0.001 via x402 with URL), and CC BY-SA 4.0 attribution requirements. That is real operational context an agent cannot get from the schema; only return-failure modes are unstated.

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?

One dense, front-loaded block that leads with what is returned and closes with cost/quota, so nothing is buried. It reads as a run-on list, but nearly every clause (attribution, latency, pricing) 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?

With no output schema, the enumerated return fields, latency, quota, and licensing make the definition largely self-sufficient for a two-parameter read tool. Only error/fuzzy-match-miss behavior is left unspecified.

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%, with both parameters documented inline, so the baseline is 3. The description's "fuzzy title search" and "any language edition" add only marginal meaning beyond the schema's own "Article title or search words" and "Wikipedia language code, default en."

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 ("Get the lead summary of a Wikipedia article in any language edition") and enumerates the returned fields, so the agent knows exactly what it gets. No sibling tool overlaps this scope, so differentiation is implicit but unambiguous.

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?

Implies usage through "Fuzzy title search" and "any language edition," and the pricing/quota lines tell the agent about cost constraints. However it never states when to prefer this over another approach (e.g., full-article retrieval) or any exclusions/limitations on when the call will fail.

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.

Resources