Skip to main content
Glama

PolySignals.net

One coin's readings

get_coin_signal
Read-only

One coin in full: the overall call, each window running now (5m, 15m, 1h, 4h, 1d) blended across venues with score, up probability, confidence and the move since the window opened, the next windows, each venue's own reading, the daily regime call, the Cryptohopper markets that get its signals and its latest delivery, the live backtest, and the newest headlines that name it. Pass timeframe to narrow it to one window.

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

Input Schema

NameRequiredDescriptionDefault
coinYesCoin ticker or name as on the site, for example BTC, ETH or SOL
timeframeNoOnly this window

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this as a read-only, closed-world operation. The description adds substantial behavioral context by explaining that readings are blended across venues and by enumerating the aggregate, per-venue, regime, market-delivery, backtest, and headline sections returned.

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?

It is a single long sentence, but it is front-loaded with 'One coin in full' and every clause enumerates a returned component rather than repeating the name. The density is justified for an aggregate tool, though the prose could be easier to scan.

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?

For a complex, multi-section aggregate with no output schema, the description covers the important return categories and the timeframe narrowing behavior. Combined with annotations covering read-only status and a fully documented two-parameter schema, an agent has enough to call it correctly.

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?

Schema coverage is 100% and both parameters have descriptions/enums, so the schema already documents coin and timeframe. The description reinforces that timeframe narrows to one of the listed windows but adds no syntax or format beyond schema.

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 opens with 'One coin in full' and enumerates the full payload—window calls, venue readings, regime, markets, backtest and headlines—so the resource and scope are unmistakable. It is clear but does not explicitly name a sibling tool or contrast its role with get_overview/get_news.

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?

It tells the agent to pass timeframe to narrow to one window, which is a parameter-use instruction rather than a tool-selection rule. There is no explicit when-to-use/when-not or alternative such as get_news or get_signal_markets, so usage is only implied by the full-payload framing.

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