Skip to main content
Glama

wiki_summary

Read-only

Short Wikipedia extract for up to 3 titles or search queries (optional lang). Returns extract, URL, thumbnail, Wikidata id and CC BY-SA 4.0 attribution. Price: 0.005 USDC per call (x402, Base).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wiki_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
itemsNo
queryNo
titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value beyond them: a per-call price of 0.005 USDC via x402 on Base, plus the CC BY-SA 4.0 attribution returned with results, which signals downstream licensing obligations. It does not cover failure modes or what happens when no parameter is supplied, keeping it below a 5.

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?

Three short sentences, front-loaded with the capability, then return fields, then price. Every clause carries information an agent would otherwise have to guess at.

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?

With no output schema, the description correctly enumerates the returned fields (extract, URL, thumbnail, Wikidata id, attribution), and it discloses the paid x402 cost the agent must account for. The only mild gap is behavior with zero arguments, despite all parameters being optional.

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 0%, so the description must carry the parameter burden. It does clarify that lang is optional and that up to 3 titles/queries can be batched via the items array, but it leaves the relationship between the top-level title, query and items ambiguous and never mentions the 300-character limits.

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?

The description names the resource and the operation (short Wikipedia extract) and adds concrete scope: up to 3 titles or search queries, optional lang. An agent can tell immediately what it returns. It stops short of a 5 only because no sibling overlap is addressed, though the listed siblings are unrelated utilities.

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 when-to-use or when-not-to-use guidance, and no routing between this and any alternative. The word 'short' hints that fuller content lives elsewhere but never says so, and nothing explains when to prefer title vs query vs the items array.

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