Skip to main content
Glama

TallyForge Quant Signals

Crypto Market Regime Snapshot

market_regime_snapshot

Returns a current market regime read for a major crypto asset from free public daily data: trend (SMA20/50/200), momentum (RSI14), realized volatility state, 1/7/30/90-day change, 1-year range and drawdown, plus a one-line summary.

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": {
      "symbol": "<symbol>"
    },
    "name": "market_regime_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesCrypto ticker quoted in USD on Coinbase, e.g. BTC, ETH, SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full load; "Returns" plus "current ... from free public daily data" establishes a read-only, daily-close snapshot sourced from free public data, which is useful context. It says nothing about freshness/latency, rate limits, or behavior when history is insufficient for SMA200, leaving meaningful gaps for an unannotated tool.

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?

One front-loaded sentence that opens with the verb and resource before enumerating contents, so the reader can stop early. The parenthetical indicator list is dense but each item is a real returnable signal rather than filler.

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 sensibly enumerates the returned fields, which is exactly the right compensation. Remaining gaps are data freshness and the preconditions for 200-day indicators, minor for a one-parameter read-only snapshot.

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?

The single parameter has 100% schema description coverage including an explicit 34-value enum and Coinbase-quoted-USD note, so the schema does the work and baseline 3 applies. The description never mentions the symbol parameter or any constraint on it, adding no meaning beyond the 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?

"Returns a current market regime read for a major crypto asset" names a specific verb and resource, and the parenthetical list (SMA20/50/200, RSI14, realized vol state, multi-horizon changes, 1-year range/drawdown) makes the aggregate-snapshot nature concrete. It does not explicitly distinguish itself from volatility_snapshot, whose territory it partially overlaps, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance and no named alternative. "From free public daily data" implies daily granularity rather than intraday, but the agent must infer whether to reach for this or volatility_snapshot/perp_funding_snapshot.

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