Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

crypto-news

[x402 paid: $0.001 USDC on Base] Top crypto headlines with links, aggregated live from Cointelegraph, Decrypt and Bitcoin Magazine RSS. tools/call returns the live payment challenge.

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": "crypto-news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoexample: 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 load, and it does disclose the key non-obvious behavior: a $0.001 USDC charge on Base via x402 and that tools/call returns the live payment challenge. It does not cover freshness/caching, failure modes when payment is not completed, or the structure of the returned items beyond 'links'.

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 sentences, payment terms front-loaded in a bracket, then capability, then a note on payment flow. Nothing is wasted, though the final clause about tools/call is terse enough to be ambiguous.

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 simple one-parameter read tool with no output schema, the coverage of purpose, sources, and cost is adequate. The gap is the payment mechanics: 'returns the live payment challenge' tells an agent a challenge exists but not what to do with it, which matters for invocation success.

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% for the single optional limit parameter, so the schema does the documentation work and baseline 3 applies. The description adds no meaning about what limit counts against or its accepted values, and notably the schema types limit as a string, which the description does not clarify.

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 a specific resource and scope (top crypto headlines with links) and identifies the three upstream sources, so an agent knows exactly what it returns. It stops short of explicitly distinguishing itself from news-adjacent siblings such as tool_crypto_news or tool_ai_news-brief.

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 statement of when to use this tool versus the other news or market siblings, and no conditions or exclusions. The only usage-relevant information is the payment tag, which is a cost note rather than selection guidance.

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