Skip to main content
Glama

A Wikipedia page summary by title or search words, in any

wiki
Read-only

A Wikipedia page summary by title or search words, in any language: title, short description, summary, page URL, thumbnail and Wikidata ID. For organisations, people and places, Wikidata facts: official website, inception, country, headquarters, date of birth and coordinates. Text is CC BY-SA 4.0 with attribution. Not found returns search suggestions. Takes about 13 s; allow a 30 s timeout. Related tools on this server, for a different need: wiki_pageviews when you need daily or monthly page views for up to 5 articles in one. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesA page title, or search words
langNoWikipedia language code, default en

Output Schema

NameRequiredDescriptionDefault
urlNo
langNo
factsNo
foundNo
titleNo
sourceNo
licenseNo
summaryNo
checkedAtNo
thumbnailNo
wikidataIdNo
attributionNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "attribution": {},
      +    "checkedAt": {},
      +    "description": {},
      +    "facts": {},
      +    "found": {},
      +    "lang": {},
      +    "license": {},
      +    "source": {},
      +    "summary": {},
      +    "thumbnail": {},
      +    "title": {},
      +    "url": {},
      +    "wikidataId": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuine operational context the annotations don't: ~13 s latency with a 30 s timeout recommendation, $0.002 per successful call with failed calls free, and CC BY-SA attribution requirements. What it does not add is much about result shape limits (truncation, length caps, payload size) beyond listing fields, which an agent invoking a paid 13-second call would want.

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?

Purpose is front-loaded in the first clause, followed by output fields, then guidance, then cost/latency. Every sentence carries information, though the pricing and network detail (USDC on Base, Solana and 10 more) is dense and slightly ahead of what an agent needs at selection time. Minor packing, no filler.

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 an output schema present and annotations covering safety, the description fills in the gaps that matter: latency, timeout advice, error behavior, licensing and cost. It is nearly complete; the only omission is any note on summary length or pagination/truncation behavior, which is a small residual gap for a paid slow call.

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%, so both parameters (q, lang) are already documented, and the description largely restates them ('by title or search words', 'in any language'). The phrase 'in any language' does confirm that lang accepts arbitrary Wikipedia language codes rather than an enumerated set, but it adds no format or default guidance beyond the schema. Baseline 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 and resource ('A Wikipedia page summary by title or search words, in any language') and enumerates what comes back (title, short description, summary, page URL, thumbnail, Wikidata ID, plus Wikidata facts for people/places/orgs). It also names the sibling it is not for (wiki_pageviews), so an agent can distinguish it without opening a schema.

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

Usage Guidelines4/5

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

Gives an explicit routing rule: use wiki_pageviews 'when you need daily or monthly page views for up to 5 articles in one.' It also tells the agent what happens on a miss ('Not found returns search suggestions'), which is a real usage consideration. It stops short of stating when this tool is the wrong choice for other needs (e.g. full article text vs summary), so it is clear but not exhaustive.

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