Skip to main content
Glama

wikipedia

Read-only

Retrieve a topic’s summary or full article text in any language, with optional language selection and full-text mode.

Instructions

Wikipedia summary (or full text) of a topic, any language.

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": {
      "query": "<query>"
    },
    "name": "wikipedia"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNo
langNodefault en
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's added burden is light. It does contribute real information beyond annotations by disclosing that output can be either a summary or full text depending on a flag, which matters for output size. It omits failure behavior (missing article, disambiguation pages) and network dependency, so it is adequate rather than rich.

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 sentence, front-loaded with the resource and the output modes, with zero filler. Its terseness borders on under-specification, which is a completeness issue rather than a structure one, but a slightly longer sentence could have resolved the query semantics at no real cost.

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

Completeness3/5

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

For a simple three-parameter read tool with annotations covering safety and no output schema, the description covers the essentials: what it returns and the language dimension. Gaps remain on how 'query' is interpreted and what happens on no match, which an agent would need in order to call it confidently.

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 only 33%, with only 'lang' documented (default en), so the description must carry weight for 'query' and 'full'. It partially does: 'full text' clearly maps to the 'full' flag and 'any language' maps to 'lang'. The required 'query' parameter's semantics — topic string, exact title matching, ambiguity handling — are never explained, leaving the most important parameter under-specified.

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

Purpose4/5

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

States a specific resource (Wikipedia) and a specific operation (fetch summary or full text of a topic, any language). An agent can immediately tell this is the Wikipedia lookup tool and no sibling overlaps that resource. It falls short of a 5 only because the title/subject semantics (exact article title vs. free-text topic) are not resolved.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no exclusion or alternative named. The agent must infer from the word 'Wikipedia' that this is for encyclopedic lookups, and nothing says whether to prefer it over generic http or extract tools for web content.

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