Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

crypto_news

[$0.001] Get real-time cryptocurrency and DeFi news headlines enriched with per-article sentiment scores and mentioned token tickers in structured JSON.

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
qNoFilter headlines by text (e.g. 'ETF', 'stablecoin')
sortNoquality (freshness + outlet + coverage, default) or newestquality
assetNoAlias of ticker (e.g. USDC, BTC, ETH)
limitNoMax articles (default 10)
tickerNoOnly articles mentioning this ticker (BTC, ETH, SOL, USDC...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose several useful traits without annotations: the operation is a read, results are structured JSON, each article carries sentiment and ticker metadata, and each call costs $0.001. It does not say whether sentiment is present on every article, how many results are typical, whether results are paginated, or how quickly the feed refreshes.

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?

A single dense sentence with the price tag front-loaded in brackets, followed by the resource, then the enrichment payload. Every clause carries information; the only mild inefficiency is that 'structured JSON' restates an obvious API property.

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?

There is no output schema, yet the description names exactly what comes back (headlines, sentiment scores, ticker mentions) and in what form, and it discloses the cost. Combined with a fully documented five-parameter schema, an agent has everything needed to decide on and invoke this tool correctly; refresh cadence and pagination are the only minor omissions.

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% and every parameter (q, sort, asset, limit, ticker) is documented with examples and an enum, so the baseline is 3. The description adds no extra parameter meaning — notably it does not clarify the q vs ticker vs asset relationship (asset is described as an alias only in the schema) or when the 'quality' sort should be preferred over 'newest'.

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?

States a specific verb and resource ('Get real-time cryptocurrency and DeFi news headlines') and adds the differentiating value proposition: per-article sentiment scores and mentioned token tickers. An agent can tell this apart from a generic 'news' tool by the sentiment/ticker enrichment, though the description never explicitly contrasts with the sibling 'news' or 'trends' tools.

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?

Usage is only implied by the purpose statement — an agent can infer 'use this when you need current crypto headlines with sentiment'. There is no explicit when-to-use/when-not guidance, no mention of prerequisites (auth, credits beyond the price tag), and no routing to alternatives for plain news or historical research.

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