Skip to main content
Glama

PolySignals.net

Daily regime calls

get_regime
Read-only

The daily regime (trend) rule relayed to Cryptohopper: long while the Coinbase daily close is more than one 20-day sigma above its 50-day average, flat once more than one below. Without a coin: the board for every coin; with a coin: its call, distance, days in state and the close that would change it.

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

Input Schema

NameRequiredDescriptionDefault
coinNoCoin ticker or name as on the site, for example BTC, ETH or SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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, so safety is covered. Beyond that, the description discloses the exact regime rule, the no-coin versus coin response shape, and the fields returned for a coin (call, distance, days in state, and the close that would change it), which is meaningful context not present in the structured fields.

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 definition is dense but front-loaded: the rule comes first, then the two modes. Every sentence carries information, though the rule sentence is long enough that it could be broken for easier scanning.

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 single-parameter tool with no output schema, the description gives enough to call it correctly and even sketches the return contents. It stops short of full completeness only because it does not relate the tool to its siblings or describe pagination or error behavior.

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%, so the baseline is 3, but the description adds value by explaining what omitting the coin does (returns the board for every coin) and what supplying it yields. That semantic distinction is more useful than the schema's bare ticker description.

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?

It names a specific rule and the exact condition that defines it: long while the Coinbase daily close is more than one 20-day sigma above its 50-day average, flat once more than one below. It also cleanly splits the two modes of operation, board for every coin versus a single coin's call, so an agent can distinguish it from siblings such as get_coin_signal or get_trend_changes.

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?

The description makes the with-coin versus without-coin behavior clear, which implicitly tells an agent when each mode applies. However, it never names an alternative sibling or states when to prefer get_coin_signal, get_trend_changes, or get_methodology instead, leaving that routing 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