Skip to main content
Glama

PolySignals.net

Daily trend changes

get_trend_changes
Read-only

The coins whose daily trend (regime) call changed, newest decision first: turned long (sent to Cryptohopper as a buy signal) or turned flat (a sell), decided at 00:05 UTC on the daily close, plus the next decision time, the coins whose live price is closest to the level that would change their call, how many Cryptohopper markets accepted each recent signal, and how many coins were long after each daily close over the last 90 days. A coin's starting call is not listed as a change. Give a coin for that coin alone: its current call, since when, whether it began as a change, and its calls over the last 90 closes.

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

Input Schema

NameRequiredDescriptionDefault
coinNoOnly this coin, for example SOL: its current trend call and when it last changed
limitNoDecisions to list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description still adds real behavioral context: decisions land at 00:05 UTC on the daily close, the window is the last 90 closes, and a coin's starting call is explicitly not reported as a change — an important edge case. The phrase 'sent to Cryptohopper as a buy signal' describes the underlying system's action rather than a write by this tool, so it isn't a hard contradiction, though it's mildly open to misreading.

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

Conciseness3/5

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

Front-loaded with the main purpose in the first clause, but the two sentences are dense run-ons that pack in four auxiliary outputs (closest-to-flip coins, market acceptance counts, 90-day breadth) with semicolon-free comma chaining. Useful content, but the structure makes it harder to parse than it needs to be.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, listing each block of the response and the per-coin variant. It omits how results paginate or truncate beyond `limit`, which is the only notable gap for a read-only reporting tool.

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% (baseline 3), and the description goes further by explaining what the `coin` filter actually yields: current call, since when, whether it began as a change, and its calls over the last 90 closes. `limit` is only obliquely covered via 'newest decision first', so it isn't a full 5.

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?

Names a specific resource and filter — coins whose daily trend/regime call changed, newest decision first — plus an explicit single-coin mode via the `coin` parameter. It never states a verb and doesn't say how it differs from siblings like get_regime or get_coin_signal, which is the main gap.

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?

'Give a coin for that coin alone' implies the two modes (change feed vs. per-coin detail) and how to pick between them, which is genuine usage guidance. But it never names an alternative tool or says when to prefer this over get_regime/get_coin_signal, so routing is left to inference.

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