Crypto News Sentiment (x402)

Sentiment Archive Coverage (free)

get_archive_coverage

Read-onlyIdempotent

Check hourly sentiment archive coverage per symbol, including reading dates, row counts, missing hours, and 7-day headline coverage, before fetching history to pick a range with data.

Instructions

Free: what the hourly sentiment archive holds (GET /archive). No wallet
needed.

Per symbol: first and latest reading, row counts, missing hours, and
coverage_7d_pct, the share of the last 7 days' logged hours that had at
least one matching headline (with hours_with_headlines_7d and
hours_logged_7d). Check it before get_sentiment_history to pick a symbol
and range with data: low-coverage coins often get no_headlines_in_range
from get_sentiment_history or "insufficient recent news" from
get_sentiment, both refused and 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": "get_archive_coverage"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Nov 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior, but the description adds useful context beyond them: it is free, requires no wallet, maps to GET /archive, and explains that low-coverage symbols cause refused and uncharged errors in sibling tools. It does not discuss rate limits or pagination, but the added cost/auth and downstream-error context is substantial.

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?

The description is compact and front-loaded: availability and cost come first, then the per-symbol fields, then the practical routing guidance. It is dense but every sentence serves a purpose; minor field enumeration is somewhat redundant with the output schema but still operationally useful.

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?

Given zero parameters, rich annotations, and an output schema, the description supplies the remaining context an agent needs: free access, no wallet requirement, endpoint, what coverage means, and when to call it relative to siblings. Nothing essential for correct selection or invocation appears 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?

There are zero parameters, so the baseline is 4. The description does not need to explain parameter usage, and its field-level explanation is supplemental rather than required.

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 description states a specific verb and resource: it reports what the hourly sentiment archive holds, per symbol, including first/latest reading, row counts, missing hours, and 7-day coverage percentage. It is clearly distinguishable from siblings by its coverage-audit purpose and its explicit role as a pre-check for get_sentiment_history.

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 explicitly says to check this before get_sentiment_history to pick a symbol and range with data, and explains what happens with low-coverage coins in get_sentiment_history and get_sentiment. This gives clear when-to-use guidance tied to concrete sibling failure modes.

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

Deploy Server