Skip to main content
Glama
Sign In

cryptonews.is

by is.cryptonews
OverviewDiscussionsAdmin

Sentiment history

get_sentiment_history
Read-only

Standard and Pro: sentiment history (Standard: 30 days back). recorded_from: minute history is recorded from 2026-10-29T02:17Z; earlier ranges return only the native’s live history or nothing. resolution defaults to auto (target 300 points); raw keeps all; buckets use the last sample score at the bucket start. Returns resolved resolution and available_from, the earliest returned point or null.

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_sentiment_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
windowNo
resolutionNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

The description adds rich behavior beyond the annotations: tier-based retention, the recorded_from cutoff that causes earlier ranges to return only live history or nothing, resolution defaults and semantics (auto targets 300 points, raw keeps all, buckets use last sample score), and return fields (resolved resolution, available_from). This is exactly the kind of operational context an agent needs.

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 dense and front-loads the most important plan/retention constraint. It uses semicolons effectively, though some phrases like 'buckets use the last sample score at the bucket start' are cryptic and could be clearer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with no output schema, the description covers availability constraints, resolution semantics, and the two return fields. It is nearly complete, missing only explicit explanation of how window relates to from/to and a fuller picture of the returned data points.

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?

With 0% schema description coverage, the description must compensate. It explains the resolution parameter thoroughly and implies time-range behavior via recorded_from and 'earlier ranges', but leaves the from/to and window parameters unexplained and their interaction ambiguous.

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?

The description states 'sentiment history' and clarifies plan limits, so the resource is clear. It doesn't explicitly contrast with the sibling get_sentiment (current sentiment), but the name and historical framing make the purpose distinguishable.

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 implied through retention details (Standard 30 days back, minute history recorded from a specific timestamp), which tells when data is available. However, there is no explicit guidance on when to use this tool versus siblings like get_sentiment, nor any alternative recommendations.

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

All cryptonews.is toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources