Skip to main content
Glama

BRAINIAC Options Analytics

Compute 25-delta skew metrics

options-analytics_skew-metrics
Read-onlyIdempotent

Compute 25-delta risk reversal, butterfly, skew slope and term-structure slope from strike and implied volatility quotes by expiry, with linear interpolation in log-moneyness and no extrapolation. Price $0.03 USDC. POST /api/v1/options-analytics/skew-metrics. 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>",
      "expiries": "<expiries>"
    },
    "name": "options-analytics_skew-metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNorate, number, from -0.2 to 1. Required.
spotYesspot, number. Required.
expiriesYesexpiries, array. Required.
dividendYieldNodividendYield, number, from -0.2 to 1. Required.
deltaConventionNodeltaConvention, string, one of spot, forward. Required.spot

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
sourcesNosources. Array.
expiriesNoexpiries. Array.
termSlopeNotermSlope. Null.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the numerical method (linear interpolation in log-moneyness, no extrapolation), the cost ($0.03 USDC), the transport (POST endpoint), and crucially the failure mode: an unpaid call returns x402 payment terms and does not compute. That is exactly the extra behavioral context annotations cannot carry.

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 compact sentences: what is computed and how, then price and endpoint, then payment behavior. The core purpose is front-loaded and every clause carries information an agent needs.

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?

An output schema exists, so return values need not be described, and the math and payment behavior are covered. The one notable gap is what happens when the supplied quotes do not bracket the 25-delta strikes, given the stated no-extrapolation rule — that could mean errors or null outputs.

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 description coverage is 100%, so the schema already documents spot, rate, dividendYield, expiries and deltaConvention. The description confirms the quote structure (strike/IV by expiry) but adds no new semantics such as how deltaConvention affects the 25-delta strike selection. 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 gives a precise verb ('Compute') plus the exact output set: 25-delta risk reversal, butterfly, skew slope and term-structure slope, and names the inputs (strike and IV quotes by expiry). It is far more specific than the title alone. It does not explicitly contrast with the nearest sibling (volatility-surface-fit), so it falls 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 Guidelines3/5

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

Usage is implied by the output list and the interpolation rule, and the payment note tells the agent a call may not execute without payment. However, there is no explicit guidance on when to choose this over volatility-surface-fit or the greeks tools, and no stated prerequisites (e.g., needing quotes bracketing the 25-delta strikes).

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