Skip to main content
Glama

wikipedia_summary

Read-onlyIdempotent

Fetch a short Wikipedia summary by exact page title, with optional language selection and no API key required.

Instructions

Get a short Wikipedia summary for a page title. No key 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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikipedia language code (default en)
titleYesExact page title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive, so the safety profile is set. The description still adds real value with 'No key needed' (auth requirement) and 'short' (output is truncated), but says nothing about behavior for missing/disambiguation pages or language fallback.

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?

Two terse sentences, front-loading the operation and then the notable constraint (no API key). Nothing is wasted.

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 read tool with full annotations and 100% schema coverage, most needs are met. However, it omits the sibling differentiation (summary vs full page vs search) and any note about missing-page behavior, which are the gaps an agent would care about.

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 description coverage is 100%, so both language and title are already documented in the schema. The description merely restates 'page title' and does not mention the lang parameter or clarify title-exactness beyond what the schema says, so baseline 3 applies.

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 verb (get) and resource (Wikipedia summary), plus the input it needs (page title). It does not differentiate from the sibling wikipedia_page (full article) or wikipedia_search, leaving the agent to infer that 'summary' is the shorter variant.

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?

The word 'summary' implies you use it when you want a brief synopsis rather than the full page, but the description never says when to prefer wikipedia_page or wikipedia_search instead. Routing between the three Wikipedia tools is left entirely to inference.

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

Deploy Server

Other Tools