Skip to main content
Glama

Wikipedia top articles (x402)

Trending on Wikipedia: the most-viewed articles of a day in any language edition with views and links, special pages rem

wikipedia_top_articles
Read-onlyIdempotent

Trending on Wikipedia: the most-viewed articles of a day in any language edition with views and links, special pages removed (lang=en, date=YYYY-MM-DD default yesterday, count=25). For news, trend and content agents. Pay per call $0.005 USDC on Base via x402.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, default yesterday
langNoWikipedia language code, default en
countNohow many 1-100, default 25
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add operational context — and it does: it discloses that special pages are removed from results and that each call costs $0.005 USDC on Base via x402. The payment model is exactly the kind of behavior an agent must know before invoking, though the payment handshake itself is only explained in the schema.

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?

The definition is dense but front-loaded: resource and filters appear first, audience and pricing trail. The parenthetical default block is somewhat redundant with the schema, but nothing is padded or vague.

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?

There is no output schema, yet the description signals the return shape ('with views and links') and the post-filter content, plus the metered payment requirement. For a four-parameter, zero-required read tool this is nearly complete; only explicit return-field detail is absent, which is a minor residual gap.

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 all four parameters are already documented with the same defaults the description repeats (lang=en, date=yesterday, count=25). The description therefore restates rather than extends schema meaning, which is the baseline-3 case; it notably does not clarify that count is typed as a string despite the 1-100 range.

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?

The description names a specific resource and scope: the most-viewed Wikipedia articles for a single day in any language edition, including views and links, with special pages filtered out. An agent can tell exactly what data comes back without opening the schema, and no sibling tool in the catalog competes with this capability.

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 line 'For news, trend and content agents' implies the usage context but never states when to choose this tool versus another source, nor any exclusions or prerequisites. The usage signal is suggestive rather than directive, so it lands at the minimum-viable level.

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