Skip to main content
Glama

BRAINIAC Options Analytics

Solve implied volatility for option prices

options-analytics_implied-volatility-solve
Read-onlyIdempotent

Solve implied volatility for 1 to 500 option prices with Newton and Brent root-finding on Black-Scholes-Merton, or on a Cox-Ross-Rubinstein tree for American options. Prices outside the no-arbitrage bounds return a status instead of a number. Price $0.04 USDC. POST /api/v1/options-analytics/implied-volatility-solve. 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>",
      "options": "<options>"
    },
    "name": "options-analytics_implied-volatility-solve"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNorate, number, from -0.2 to 1. Required.
spotYesspot, number. Required.
styleNostyle, string, one of european, american. Required.european
optionsYesoptions, array. Required.
treeStepsNotreeSteps, integer, from 50 to 2000. Required.
dividendYieldNodividendYield, number, from -0.2 to 1. Required.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
resultsNoresults. Array.
sourcesNosources. Array.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses the key behavioral facts an agent cannot guess: prices outside no-arbitrage bounds return a status rather than a number, the call is paid ($0.04 USDC via x402), and an unpaid call returns payment terms without executing. It does not discuss convergence failure or tolerance, which is the main remaining gap.

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?

Four tight sentences, front-loaded with the operation and scope, then model choice, then failure semantics, then price/endpoint/payment. No sentence is filler and no repetition of the title.

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?

For a stateless compute endpoint with an output schema and full annotations, this covers what an agent actually needs before calling: input scale limit, model selection by exercise style, out-of-bounds response behavior, and the payment gate that blocks execution. Return-value details are correctly left to the output schema.

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; the description adds meaning on top by stating the 1-to-500 batch limit (not encoded as maxItems in the schema) and by tying 'style: american' to the CRR tree path, which implicitly gives significance to treeSteps. It adds nothing about rate/dividendYield conventions, but that is already schema-documented.

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 ('Solve implied volatility ... for option prices') plus batch scope (1 to 500) and the two numerical methods (Newton/Brent on Black-Scholes-Merton, CRR tree for American). That combination makes it distinguishable from the sibling pricing/Greeks tools, which go the other direction (inputs -> price).

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: you call it when you already have observed option prices and want the vol back out, and the 'American options' clause tells the agent which model branch applies. However, there is no explicit when-not guidance and no routing to alternatives such as historical-volatility (realized vol) or volatility-surface-fit (multi-strike surface), so selection relies on the agent inferring from the name.

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