Skip to main content
Glama

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

tool_crypto_news

[x402 paid: $0.002 USDC on Base] Crypto headlines with links from live RSS feeds. 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": "tool_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 burden, and it does disclose two important behaviors: the call is paid ($0.002 USDC on Base) and an unpaid tools/call returns a live payment challenge (implying a 402 flow). It stops short of explaining how to satisfy the challenge, whether the call has side effects, or any rate limits, so key behavioral context is still missing.

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 with the price front-loaded in brackets and the return behavior immediately after. Every sentence carries information, though the bracketed prefix is dense and slightly cryptic to an agent unfamiliar with x402.

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-optional-parameter, no-output-schema tool, the description covers the resource and the payment mechanic, which is the essential piece. It leaves gaps on what a successful paid response looks like (count, freshness, link format) and on the limit parameter's meaning, which matters for an agent deciding how to call it.

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 already documents it. The description adds nothing about what limit counts (headlines per feed? total?) or valid ranges, so the baseline of 3 applies.

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 ('Crypto headlines with links from live RSS feeds'), so an agent knows it returns news items with URLs rather than prices or sentiment. It does not differentiate itself from the similarly named sibling 'crypto-news', leaving a small ambiguity about which to pick.

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 alternatives, no exclusions, and no mention of prerequisites such as a funded wallet before calling. The only routing-adjacent content is the price tag and the payment-challenge note, which describe invocation mechanics rather than usage selection.

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