Skip to main content
Glama

BRAINIAC Options Analytics

Compute market-implied expected move

options-analytics_expected-move
Read-onlyIdempotent

Compute the one and two standard deviation expected move and price ranges from implied volatility or from the at-the-money straddle price. Price $0.02 USDC. POST /api/v1/options-analytics/expected-move. An unpaid call returns the x402 payment terms and does not run.

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": {
      "spot": "<spot>",
      "daysToExpiry": "<daysToExpiry>"
    },
    "name": "options-analytics_expected-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
ivNoiv, value. Optional.
spotYesspot, number. Required.
dayBasisNodayBasis, value. Required.
daysToExpiryYesdaysToExpiry, number, from any to 3650. Required.
straddlePriceNostraddlePrice, value. Optional.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
methodNomethod. String.
range1Norange1. Array.
range2Norange2. Array.
sourcesNosources. Array.
oneSigmaNooneSigma. Number.
twoSigmaNotwoSigma. Number.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.
ivFromStraddleNoivFromStraddle. Null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, but the description adds information the annotations cannot carry: a concrete price ($0.02 USDC), the POST endpoint, and critically that an unpaid call returns x402 payment terms without executing. That last sentence is exactly the kind of behavioral disclosure an agent needs before invoking a paid endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the computation, then the cost and endpoint, then the payment failure mode. Every sentence carries distinct information with no filler or repetition of the schema.

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 a full output schema, complete annotations and 100% parameter coverage, the description only needs to cover what structured fields cannot: input modes, cost, and the unpaid-call behavior — all of which it does. Nothing an agent needs in order to call this correctly is missing.

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 meaning beyond the schema by framing iv and straddlePrice as alternative computation routes rather than independent inputs — a relationship the schema does not express. It does not clarify what happens if both are supplied or which takes precedence, which keeps it below a 5.

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 specific verb and resource — computing one and two standard deviation expected move plus price ranges — and names the two input routes (implied volatility or ATM straddle price). That is clearly distinct from siblings like implied-volatility-solve or black-scholes-greeks, which an agent can rule out without opening either schema.

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 phrase 'from implied volatility or from the at-the-money straddle price' implicitly tells the caller which input path to supply, which is useful guidance. However, there is no explicit when-to-use/when-not guidance and no named alternative for adjacent tasks such as solving for IV, so the routing is left 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