Skip to main content
Glama

PolySignals.net

Recent history

get_history
Read-only

The blended reading of one coin's window over the last hours (up to 48), thinned to about 36 rows: time, up probability, score and confidence.

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": {
      "coin": "<coin>"
    },
    "name": "get_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin ticker or name as on the site, for example BTC, ETH or SOL
hoursNo
timeframeNo1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world safety, and the description adds genuinely non-obvious behavior: the series is downsampled ('thinned') to roughly 36 rows and capped at a 48-hour window, so an agent knows it will not receive every data point. It stops short of covering ordering, gaps, or what happens for coins with short histories.

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?

A single front-loaded sentence with the resource, window constraint, and return fields packed in without filler. It loses a point only because the compressed phrasing ('blended reading') trades clarity for brevity.

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

Completeness3/5

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

With no output schema, the description helpfully enumerates the returned columns, which is the main thing an agent needs. It is still incomplete for a three-parameter time-series tool: timeframe semantics and row ordering/interpretation of 'up probability' are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: only `coin` is documented in the schema. The description partially compensates for `hours` ('up to 48'), but `timeframe` — an enum-driven parameter that changes the granularity and therefore the meaning of the ~36 rows — is never mentioned anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names a specific resource (one coin's history over the last hours) and even lists return fields (time, up probability, score, confidence), but 'blended reading' is unexplained jargon and nothing distinguishes this from siblings like get_trend_changes or get_coin_signal, which plausibly return overlapping signal data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to pick this versus get_trend_changes, get_coin_signal, or get_results, and no stated prerequisites. The only implied usage cue is the 48-hour cap, which is a constraint rather than a selection rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources