Skip to main content
Glama

Encyclopedia Article Summary Payment Quote

wiki_summary_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/wiki/summary (base $0.003; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?title=Earth (one Wikipedia article title). Summary of one Wikipedia article by title: title, short description, plain-text lead extract, page URL, revision and timestamp, from the Wikimedia REST API. Text by Wikipedia contributors under CC BY-SA 4.0; each response carries the page link, history link and licence line, and you may reuse the text under that licence. Not affiliated with or endorsed by the Wikimedia Foundation. Not found or bad input: not charged. USDC on Base only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Beyond the readOnly/idempotent annotations, it discloses genuinely useful behavior: the tool performs no check and no payment, failed lookups are free, and payment is restricted to USDC on Base. It also warns that returned text is CC BY-SA licensed with attribution requirements. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core fact is front-loaded, but the paragraph is a run-on mixing pricing, payment protocol, data description, licensing, and a trademark disclaimer. 'USDC on Base only' appears twice and the licensing sentences are dense enough to slow parsing.

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?

For a zero-parameter quote tool with no output schema, it covers what is being priced, the price, the payment rail, and the failure/no-charge policy. The licensing and attribution notes are extra but relevant to reuse. A short note on the response shape (e.g., that it returns a 402 challenge) is the only real gap.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description mentions '?title=Earth' and 'one Wikipedia article title', but that is the parameter of the underlying HTTP API being priced, not of this tool, so it adds context rather than parameter meaning.

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 first sentence gives a specific verb and resource ('Returns the payment terms for https://horizonpulse.dev/api/wiki/summary') and explicitly negates the alternative behavior ('this tool never runs the check or pays'). The remaining sentences describe the underlying data API rather than this tool, which slightly blurs the line, but an agent can still tell what the call returns.

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?

It gives the mechanics for the next step ('Pay the 402 over HTTP with x402 v2: GET ?title=Earth') and the error policy ('not found or bad input: not charged'), which implies a quote-then-pay workflow. However, it never states explicitly when to choose this tool versus a sibling quote tool or the underlying summary endpoint, leaving selection to inference.

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.