Skip to main content
Glama

BRAINIAC Options Analytics

Fit an SVI volatility surface

options-analytics_volatility-surface-fit
Read-onlyIdempotent

Fit a raw-SVI slice per expiry to strike implied volatilities with the Zeliade quasi-explicit method, interpolate the surface in total variance, and report butterfly and calendar static-arbitrage violations. Price $0.05 USDC. POST /api/v1/options-analytics/volatility-surface-fit. 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": {
      "forwardByExpiry": "<forwardByExpiry>",
      "points": "<points>"
    },
    "name": "options-analytics_volatility-surface-fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoquery, array. Optional.
pointsYespoints, array. Required.
forwardByExpiryYesforwardByExpiry, object. Required.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
queryNoquery. Array.
slicesNoslices. Array.
sourcesNosources. Array.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.
calendarArbitrageNocalendarArbitrage. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds important context beyond that: the x402 payment requirement, the POST endpoint, and the fact that an unpaid call returns payment terms without running. It does not detail rate limits or the full auth flow, so 4 rather than 5.

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?

The definition is front-loaded with the core operation, then compactly adds pricing, endpoint, and unpaid-call behavior. Every sentence carries useful information, and there is no redundant or filler wording.

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?

For a complex analytics tool with nested parameters, an output schema, and safety annotations, the description covers purpose, method, payment/access behavior, and the arbitrage output. It leaves parameter relationships and sibling comparisons to the schema/context, which is a minor gap rather than a blocking one.

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 baseline is 3 even without parameter details in the description. The description adds useful domain context ('per expiry', 'strike implied volatilities', 'total variance') but does not explain the forwardByExpiry map, the points array, or the optional query parameter beyond what the schema already states.

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 opening clause states a specific verb and resource: fit a raw-SVI slice per expiry, using the Zeliade quasi-explicit method, interpolate in total variance, and report butterfly/calendar arbitrage violations. This clearly distinguishes it from sibling analytics such as implied-volatility solve, skew metrics, or historical volatility.

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?

The description gives clear context for when this tool is appropriate: when the agent needs an SVI volatility surface fitted to strike implied vols and checked for static-arbitrage violations. It does not explicitly compare against sibling tools or state when not to use it, so it falls short of a 5.

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