Skip to main content
Glama

Wikipedia lookup (x402)

wikipedia_lookup

Read-onlyIdempotent

$0.01 via x402: Wikipedia knowledge lookup — article titles, extract snippets and canonical URLs for any topic. The cheap fact-grounding read agents make to reduce hallucination. Free upstream (Wikimedia).

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": "wikipedia_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesTopic / search query
limitNoResults 1-10 (default 3)
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real context beyond them: the $0.01 x402 cost and the fact that the upstream source is free, which matters for an agent weighing call budget. It says nothing about result quality, truncation, or failure modes when a topic has no article.

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?

Two compact sentences with no filler, and the returned fields are named up front. The leading price tag ('$0.01 via x402') is informational but pushes the actual purpose into second position, slightly weakening front-loading.

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 description usefully enumerates what comes back (titles, snippets, URLs) and flags the cost model, which is enough for a simple 3-parameter read tool. Minor gaps remain around result limits and no-match behavior.

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 q, limit, and x_payment are already documented in the schema, including the omit-to-receive-terms payment flow. The description adds no further meaning about query syntax, ranking, or how limit affects snippet content, so the 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 ('Wikipedia knowledge lookup') plus the concrete payload returned ('article titles, extract snippets and canonical URLs'). Naming Wikipedia as the source distinguishes it from generic siblings like web_search, read_links, and papers_search without needing to name them.

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?

The phrase 'cheap fact-grounding read agents make to reduce hallucination' gives a clear intended use case and decision context (low-cost fact grounding). It stops short of explicit exclusions or naming an alternative tool for non-Wikipedia needs, so it lacks the when-not guidance of a 5.

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