Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

get_crypto_news

Paid $0.02 (x402, USDC Base): top crypto headlines aggregated from Cointelegraph/Decrypt/NewsBTC RSS with per-article source links and publish times. Daily brief for trading and research agents.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 behavioral burden, and it does disclose a significant trait: the tool is paid ($0.02 via x402, USDC Base). That payment/auth requirement is genuinely useful context an agent cannot get from structured fields. However, it omits what happens on payment failure, freshness/caching of the feed, result count limits, and rate constraints, leaving real gaps for a zero-annotation tool.

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, with the cost and payment rail front-loaded before the content description, which is the right ordering. The trailing "Daily brief for trading and research agents" is mild positioning language rather than operational information, but it is short enough not to waste much space.

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, no-annotation tool with no output schema, the description covers the essentials: what it returns (headlines with source links and publish times), where the data comes from, and what it costs. It falls short only on operational details like freshness cadence and result volume, which an agent would need to call it with confidence.

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 no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. Nothing in the description conflicts with the empty schema.

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 verb and resource ("top crypto headlines aggregated from Cointelegraph/Decrypt/NewsBTC RSS") and states the return shape (per-article source links and publish times). This clearly separates it from siblings like get_market_pulse, get_crypto_price, and research_report.

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?

"Daily brief for trading and research agents" implies the intended use case, but there is no explicit when-to-use vs when-not guidance and no routing to alternatives such as research_report or get_market_pulse. The agent must infer that this is the news-feed option rather than a price or analysis tool.

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