Skip to main content
Glama

TallyForge Quant Signals

Crypto Volatility Snapshot

volatility_snapshot

Realized volatility for a major crypto asset: 7/30/90-day annualized close-to-close vol, 30-day Parkinson (high-low) vol, ATR14 as % of price, where today's 30-day vol sits in its 1-year range (percentile, low/normal/high), whether vol is expanding or contracting, and 1-sigma expected moves for 1/7/30 days. Useful for position sizing and stop placement.

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": "volatility_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

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It thoroughly describes what is returned, which implicitly signals a read-only analytical operation, but it says nothing about data freshness/caching, latency, rate limits, or what happens for assets with short history. Useful content, but material operational behavior is undisclosed.

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?

Two sentences, front-loaded with the core resource and then a compact metric enumeration, closing with intended use. Dense but every clause maps to a real output field; only slight cost is the long comma-separated list, which is nonetheless informative 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 must explain return values, and it does so field by field, including units (annualized, % of price, percentile) and the 1-sigma horizons. The main remaining gap is data provenance and freshness, which matters for a volatility snapshot used in sizing decisions.

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 the sole parameter has an explicit enum with a description ('Crypto ticker quoted in USD on Coinbase'). The phrase 'a major crypto asset' loosely frames the universe, but adds no meaning about the symbol beyond what the schema already states, so the baseline of 3 applies.

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?

The description names the specific resource (realized volatility for a single crypto asset) and enumerates the exact metrics returned: 7/30/90-day annualized close-to-close vol, 30-day Parkinson vol, ATR14 as % of price, 1-year percentile band, expansion/contraction state, and 1-sigma moves. This is clearly distinguishable from siblings like market_regime_snapshot or perp_funding_snapshot.

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?

Use context is stated ('useful for position sizing and stop placement'), which implies the intended analytical scenario. However, there is no explicit when-to-use vs alternatives guidance, no exclusions, and no mention of prerequisites such as needing a full year of history for the percentile calculation.

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