Skip to main content
Glama

wiki_summary

Wikipedia summary of a topic. $0.01 USDC on Base (x402).

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one material behavioral trait: this is a paid call costing $0.01 USDC on Base via x402, which matters for agent decision-making. It says nothing about payment failure modes, rate limits, which Wikipedia language/edition is queried, or the length/shape of the returned summary.

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 short sentences, purpose front-loaded and price second, with no filler. It is efficient, though its terseness is part of why key details (payment flow, query format) are absent.

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 one-parameter tool with no output schema, the description covers what it does and its cost, which is the minimum an agent needs. It omits the payment mechanics an x402 tool requires in practice and any hint about the query format or return size, leaving real gaps for a paid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter q, and the description does not compensate: "of a topic" only loosely implies q is a topic string, without stating whether it accepts a title, a free-text query, a URL, or a language code. The schema gives a bare string with no description.

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?

"Wikipedia summary of a topic" names a specific resource and the action (return a summary of it), so an agent can tell it apart from eth_price, weather, and fetch_page. It stops short of naming what makes it distinct from a generic page fetch, but the purpose is unambiguous.

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, when-not-to-use, or alternative routing (e.g., when to prefer this over fetch_page or probe_x402). The only usage signal is an implicit one: the price note suggests it is a paid endpoint, but nothing states prerequisites such as needing an x402-capable client or funds on Base.

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