Crypto News Sentiment (x402)

Current Crypto Sentiment

crypto_sentiment

Assess a supported crypto ticker's current news sentiment with a bullish/bearish/neutral score, 72-hour headline analysis, Fear & Greed Index, and top driving headlines.

Instructions

Current news sentiment for one crypto ticker. Paid: $0.01 in USDC on Base
per call, from this MCP server's own CDP wallet.

symbol must be exactly one of the 24 uppercase tickers from
list_supported_coins (e.g. BTC). Lowercase ("btc") or any other symbol is
rejected by the input schema before a request is sent, so nothing is
charged.

Scores headlines from the last 72 hours across 9 crypto news RSS outlets
(VADER plus a crypto slang lexicon, weighted toward the newest) alongside
the Fear & Greed Index. Returns a bullish/bearish/neutral label, a
compound score (-1 to 1), sample sizes, the news and Fear & Greed values,
and up to 5 headlines that moved the score.

Low-coverage coins: when recent headlines are too few (effective sample
size below 5), the API refuses with HTTP 422 "insufficient recent news",
returned here as an error with charged: false. archive_coverage shows each
coin's coverage_7d_pct. Without CDP keys the tool returns a no-wallet
message and pays nothing. For past readings use get_hourly_history.

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Uppercase crypto ticker, one of the 24 from list_supported_coins (e.g. BTC). Stock tickers and other symbols are refused and not charged.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.4Oct 21, 2026

addedInput schema / properties / symbol / description

Added value: +"Uppercase crypto ticker, one of the 24 from list_supported_coins (e.g. BTC). Stock tickers and other symbols are refused and not charged."

addedInput schema / properties / symbol / enum

Added value: +[
+  "BTC",
+  "ETH",
+  "SOL",
+  "XRP",
+  "DOGE",
+  "ADA",
+  "AVAX",
+  "LINK",
+  "MATIC",
+  "DOT",
+  "SHIB",
+  "LTC",
+  "BNB",
+  "USDC",
+  "USDT",
+  "NEAR",
+  "HYPE",
+  "QNT",
+  "AAVE",
+  "TAO",
+  "PEPE",
+  "PUMP",
+  "ENA",
+  "STRK"
+]

First observedv0.1.2Oct 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say openWorldHint=true and readOnlyHint=false; the description supplies the crucial missing context: a $0.01 USDC charge per call from the server's own CDP wallet, no charge on schema rejection, charged:false on the HTTP 422 low-coverage path, and a no-wallet fallback that pays nothing. It also discloses the scoring method and the return payload shape, which annotations cannot convey.

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?

Purpose and cost are front-loaded, followed by input constraints, then output, then failure modes — a logical progression with no filler sentences. It runs long for a single-parameter tool, but nearly every clause carries distinct operational information.

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?

Covers payment, input validation, output fields, the low-coverage 422 failure with charged:false, the no-wallet path, and a pointer to archive_coverage for pre-checking coverage. Even though an output schema exists, the description still explains what the label and compound score mean, leaving no gap an agent would need to guess at.

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?

Schema coverage is 100% with a full enum, so the baseline is 3. The description adds real meaning beyond the schema: the uppercase-only requirement is tied to a concrete consequence (rejected before a request is sent, nothing charged), which changes how an agent validates input rather than merely restating the enum.

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?

States a specific verb and resource — 'Current news sentiment for one crypto ticker' — and immediately scopes it to 72 hours of headlines plus Fear & Greed. It is clearly distinguishable from get_hourly_history (past readings) and list_supported_coins (ticker enumeration), which are both named.

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?

Explicitly routes the agent: use list_supported_coins to obtain a valid ticker, and use get_hourly_history for past readings. The rejection condition (lowercase or non-listed symbol) is stated with its consequence, so the agent knows exactly what input is acceptable before calling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server