Skip to main content
Glama

Search crypto news headlines from public RSS feeds

crypto_news
Read-only

Latest crypto headlines from the RSS feeds of CoinDesk, Cointelegraph, Decrypt, The Block and Bitcoin Magazine, newest first: title, link, publisher, publish time, the coins named in the text, and at most 200 characters of the feed's own summary. Filter by words in the text (q) or by coin. Feeds are cached 5 minutes; a feed that fails is listed in unavailable. Headlines and links only, not the articles. Related tools on this server, for a different need: crypto_candles when you need OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m; crypto_convert when you need to convert crypto and fiat amounts at the current spot rate. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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
qNoWords to match in the headline or summary, up to 100 characters (optional)
coinNoCoin ticker to filter by, e.g. BTC (optional)
limitNoHeadlines to return, 1 to 50, default 20

Output Schema

NameRequiredDescriptionDefault
countNo
itemsNo
sourceNo
checkedAtNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply readOnlyHint and openWorldHint, and the description adds substantially: 5-minute feed caching, partial-failure semantics ('a feed that fails is listed in unavailable'), truncation of summaries to 200 characters, and the full payment model ($0.002 per successful call via x402 USDC on multiple networks, failures not charged). These are precisely the operational facts an agent needs before calling.

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?

Front-loaded with purpose, sources, and return shape before routing and pricing details, so the agent can stop reading early. The pricing sentence is long and the alternatives block is somewhat dense, but no sentence is pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, open-world search tool with an output schema already present, the description covers sourcing, ordering, result fields, caching, partial-failure reporting, and cost. Nothing material to correct invocation is missing.

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 q, coin, and limit are already documented; the description restates the filter behavior ('Filter by words in the text (q) or by coin') without adding format or edge-case detail. The limit parameter is never mentioned, and the interaction between q and coin (AND vs OR) is left implicit.

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?

Opens with a specific resource and scope: 'Latest crypto headlines from the RSS feeds of CoinDesk, Cointelegraph, Decrypt, The Block and Bitcoin Magazine, newest first', enumerating the exact sources and ordering. It also declares the fields returned and explicitly bounds scope ('Headlines and links only, not the articles').

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names two alternatives with the condition that selects each: crypto_candles 'when you need OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m' and crypto_convert 'when you need to convert crypto and fiat amounts at the current spot rate'. The contrast makes clear this tool is for news headlines rather than market data or conversion.

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