Crypto News Sentiment (x402)

List Supported Coins

list_supported_coins

Read-onlyIdempotent

Discover which 24 cryptocurrency ticker symbols are supported for sentiment scoring and price quotes before sending a paid request. Free to check, no wallet or network call needed.

Instructions

Free: list the 24 ticker symbols crypto_sentiment supports, with names.

Useful before choosing a symbol for crypto_sentiment or price_quote.
No wallet needed and no network call. Any other symbol is rejected by
those tools' input schema before a request is sent, so nothing is
charged.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Oct 16, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: no wallet needed, no network call, and therefore nothing charged. It stops short of saying whether the list is static or can change, which would be the last useful detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: what it returns, when to use it, and the cost/validation guarantee. The "Free:" lead is front-loaded and every sentence carries information not available elsewhere.

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?

An output schema exists so return values need not be described, and "with names" still hints at shape. For a zero-parameter, side-effect-free lookup, the description covers purpose, routing, and cost implications completely.

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 zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly spends no words on arguments.

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 — list the 24 ticker symbols supported by crypto_sentiment — and even quantifies the result size. It is immediately distinguishable from siblings like crypto_sentiment and price_quote, which consume symbols rather than enumerate them.

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?

"Useful before choosing a symbol for crypto_sentiment or price_quote" names the exact downstream tools and the decision point that triggers this call. It also explains what happens with an unsupported symbol (rejected by those tools' input schema before a request is sent), closing the obvious follow-up question.

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

Deploy Server