Skip to main content
Glama

Max pain and corridor track record per expiry

expiry_record
Read-onlyIdempotent

How often BTC/ETH Deribit options settled at max pain, inside the market-maker breakeven corridor, and whether OI walls held, over hundreds of expiries — plus the most recent settled expiries (Deribit and Bybit max pain side by side) and the current max pain of upcoming expiries. Use for "will price pin to max pain on Friday?" type questions: it answers with the historical hit rate, not a prediction.

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": "expiry_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesUnderlying asset.
limitNo

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.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful behavioral context: multi-venue sourcing (Deribit and Bybit), a large historical sample, and the fact that the output is track record rather than forecast. It says nothing about data freshness, settlement timing, or how the history window is bounded, which matters for a statistics 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?

The core deliverable is front-loaded in the first clause and the second sentence earns its place by defining the use case and the non-predictive nature of the result. It is dense, packing three distinct data outputs into one sentence, but no wording is wasted.

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 an output schema present, return-value explanation is unnecessary, and the description adequately conveys what data families are returned for a two-parameter tool. Remaining gaps are the exact role of `limit` and the freshness/recency bounds of the historical sample.

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 only 50% and the `limit` parameter has no description in the schema; the phrase "most recent settled expiries" only implicitly hints that `limit` bounds that list. The `asset` enum is self-explanatory. Baseline 3 is right — the description neither compensates fully for nor worsens the coverage gap.

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?

States a precise resource and scope: historical settlement rates at max pain, corridor containment, OI-wall holds across hundreds of expiries, plus recent settled and upcoming max pain levels. An agent can tell this apart from general market-state or journal-style siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit usage trigger ("will price pin to max pain on Friday?" questions) and an important framing constraint (it returns historical hit rate, not a prediction). It stops short of naming alternatives or when-not-to-use conditions, so it is clear context but not full routing guidance.

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