Crypto News Sentiment (x402)

Live x402 Price of a Sentiment Call (free)

get_call_price

Read-onlyIdempotent

Reads the live x402 price and payment requirements for a get_sentiment call from an unpaid 402 response—no wallet or signature needed—so you can confirm costs before funding.

Instructions

Free: the live x402 price of one get_sentiment call, read from an
unpaid request's 402 response. Nothing is signed; no wallet needed.

When not to use it: prices are fixed at $0.01 per get_sentiment call,
$0.05 per get_sentiment_history call and $0.02 per get_movers call, so
there's no need to call this before every paid call. Use it to confirm
the live price and payment requirements, e.g. before funding a wallet.
It quotes get_sentiment only.

symbol must be exactly one of the 24 uppercase tickers from
list_supported_coins; lowercase or any other symbol is rejected by the
input schema before a request is sent. A low-coverage coin still gets a
quote; a get_sentiment call for it may then be refused with
"insufficient recent news" (not charged).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_call_price"
  }
}

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.

Addedv0.2.0Nov 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses that nothing is signed, no wallet is needed, and no charge is incurred, plus the downstream failure mode where a low-coverage coin still quotes but a get_sentiment call may be refused with "insufficient recent news" uncharged. That is behavior an agent could not infer from the annotations or schema.

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 the purpose in the first sentence, followed by the exclusion, then the parameter constraint that has a real consequence for the caller. Slightly longer than necessary with some line-wrap fragmentation, but every sentence carries 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?

For a single-parameter, free, read-only probe with an output schema already documenting return values, the description covers cost, signed-vs-unsigned behavior, scope limits, and input validation. Nothing an agent needs in order to call it correctly is missing.

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% and the enum already enforces the 24 tickers, so the baseline is 3; the description earns more by explaining the consequence of a bad symbol (rejected by the input schema before a request is sent, so no charge) and pointing at list_supported_coins as the source of truth. It does not add format detail beyond that, which is the only remaining gap.

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 opening sentence states a specific verb and resource: reading the live x402 price of one get_sentiment call from an unpaid request's 402 response. It also bounds scope explicitly ("It quotes get_sentiment only"), so an agent can distinguish it from get_movers and get_sentiment_history pricing without opening a schema.

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?

It gives an explicit "When not to use it" section with the fixed per-call prices and the reason not to call before every paid call, then names the legitimate trigger (confirming live price/payment requirements before funding a wallet). Both the exclusion and the positive case are stated.

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

Deploy Server