Skip to main content
Glama

BTC/ETH options market state with history context

market_state
Read-onlyIdempotent

Current dealer gamma regime (positive = hedging dampens moves, negative = amplifies), zero-gamma flip, call/put walls, DVOL and its 1-year rank, implied-minus-realized volatility, IV term structure and the INDICIA Fear & Greed index, with how long the regime has lasted in our daily archive. Descriptive context, not a direction call. Data refreshes about every 2 hours; the result carries as_of.

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": {
      "asset": "<asset>"
    },
    "name": "market_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesUnderlying asset.

Output Schema

NameRequiredDescriptionDefault
linkYes
as_ofYesUTC time the underlying data was computed.
staleYesTrue when the data is older than its normal refresh cycle.
caveatNo
sourceNo
summaryYes
age_hoursNoHours between as_of and the time of this answer.
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / age_hours
      Added value: +{
      +  "description": "Hours between as_of and the time of this answer.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds non-obvious behavioral context beyond that: a ~2 hour refresh cadence and an as_of field in the result, which lets the agent reason about staleness, plus the archive-based regime duration. It stops short of stating limits or failure behavior, but the added freshness metadata is substantive.

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 payload-dense clause list comes first, followed by the interpretive caveat and data-freshness note, so it is front-loaded and readable. The enumeration of indicators is long but each item carries signal; slight density is the only cost.

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?

With an output schema present, return-value detail need not be repeated, and annotations cover the safety profile. The description closes the remaining gaps an agent would care about — interpretation boundary (descriptive, not predictive) and data currency (refresh interval, as_of field) — for a simple one-parameter tool.

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?

There is a single required parameter (asset) whose enum and description are fully documented in the schema at 100% coverage. The title reinforces the BTC/ETH scope but the description text itself adds no new meaning about the parameter, so the baseline 3 applies.

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 enumerates concrete resources — dealer gamma regime, zero-gamma flip, call/put walls, DVOL with 1-year rank, implied-minus-realized vol, IV term structure, Fear & Greed — so an agent knows exactly what market state is returned. It does not explicitly contrast itself with the listed siblings, but their names (decision_journal, hypothesis_ledger, expiry_record) occupy clearly different domains, so ambiguity is low.

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?

Usage context is implied: reach for this when you need descriptive options-market context rather than a directional signal, and the sentence "Descriptive context, not a direction call" usefully bounds interpretation. However, no alternative tool is named and no explicit when-not condition is given, so the agent must infer the boundary from the phrasing.

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