Skip to main content
Glama

curatedapi

Implied volatility calculator

calc_finance_implied_volatility
Read-only

The volatility at which the Black-Scholes-Merton formula gives an option's market price, pinned between proven bounds.

Turns an option's price back into the volatility that explains it. The Black-Scholes price rises with volatility, so a price inside the option's possible range matches exactly one volatility. It is found here by closing in on it and then proving that the price is too low just below and too high just above, so the digits returned are correct. A price outside the possible range is refused with the reason.

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": {
      "option_price": "<option_price>",
      "spot": "<spot>",
      "strike": "<strike>",
      "time_to_expiry_years": "<time_to_expiry_years>",
      "risk_free_rate_percent": "<risk_free_rate_percent>",
      "option_type": "<option_type>"
    },
    "name": "calc_finance_implied_volatility"
  }
}

Input Schema

NameRequiredDescriptionDefault
spotYesThe underlying's price now. A ratio of two decimals such as "0.08/12" is accepted. Allowed: > 0 and <= 1000000000000000.
strikeYesThe option's strike price. A ratio of two decimals such as "0.08/12" is accepted. Allowed: > 0 and <= 1000000000000000.
optionsNoPrecision and rounding of the results (default: rounding=half_even, decimals=6).
option_typeYesCall or put. Options: call: the right to buy; put: the right to sell
option_priceYesThe option's market price. A ratio of two decimals such as "0.08/12" is accepted. Allowed: > 0 and <= 1000000000000000.
time_to_expiry_yearsYesTime to expiry in years. Write days as a ratio, such as "30/365". A ratio of two decimals such as "0.08/12" is accepted. Allowed: > 0 and <= 100.
dividend_yield_percentNoDividend yield per year in percent, continuously compounded. Allowed: >= -50 and <= 100. Unit: percent.0
risk_free_rate_percentYesRisk-free interest rate per year in percent, continuously compounded. Allowed: >= -50 and <= 100. Unit: percent.

Output Schema

NameRequiredDescriptionDefault
inputsYesThe inputs as understood.
resultYes
formulaNo
receiptNoOnly with ?receipt=true: a signed receipt for this answer, a JSON Web Token signed with Ed25519 (alg EdDSA). Its claims are iss, iat, jti (the request id), endpoint, date and response (this response without the receipt). Check it with the keys at /.well-known/jwks.json or POST /v1/receipts/verify.
warningsYes
exactnessYesFor each decimal output: exact; rounded (correctly, to the precision); rounded_uncertified (the last digit could not be proven); or underflow (below 1e-100, reported as 0).
precisionNoThe precision and rounding that were applied.
calculatorYesThe calculator and version that ran.
referencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, non-open-world, so the lower bar applies, and the description still adds substantive behavior: the search method (closing in, then bracketing to prove the price is too low below and too high above), a correctness guarantee on the returned digits, and a defined failure mode for out-of-range prices. It does not cover determinism vs the idempotentHint=false annotation, but nothing conflicts.

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?

Front-loaded with the core definition, followed by the mechanism and then the error case, in a sensible order. The second sentence largely restates the first ('Turns an option's price back into the volatility'), which is mild waste but not enough to obscure the tool's purpose.

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, the description need not explain return values, and it correctly focuses on the computation and on the refusal behavior an agent needs to anticipate. For an 8-parameter, nested-object calculator with full schema coverage, this is complete enough for correct invocation.

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 fully documents all eight parameters including the ratio-formatted decimals, dividend yield and rounding options. The description adds no parameter-level meaning beyond that, so the 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?

States a specific verb and resource: it computes 'the volatility at which the Black-Scholes-Merton formula gives an option's market price' — an inverse of option pricing, not a price calculation. That implicitly distinguishes it from a Black-Scholes pricing sibling, but the description never names or contrasts the sibling explicitly.

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 context is implied by the description ('Turns an option's price back into the volatility') but there is no explicit when-to-use/when-not guidance and no named alternative for the forward direction (pricing from volatility). The one exclusion present is a data condition: prices outside the possible range are refused.

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