Skip to main content
Glama

Headroom Desk options calculators

Implied volatility from an option price

implied_volatility
Read-onlyIdempotent

The Black-Scholes volatility at which the model value equals a given option price, or a message when no volatility fits that price. All inputs, including the interest rate and dividend yield, must be supplied.

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_type": "<option_type>",
      "option_price": "<option_price>",
      "underlying_price": "<underlying_price>",
      "strike": "<strike>",
      "days_to_expiry": "<days_to_expiry>",
      "rate_pct": "<rate_pct>",
      "dividend_yield_pct": "<dividend_yield_pct>"
    },
    "name": "implied_volatility"
  }
}

Input Schema

NameRequiredDescriptionDefault
strikeYesStrike in dollars.
rate_pctYesInterest rate per year in percent (0 is allowed).
option_typeYes
option_priceYesOption price per share in dollars.
days_to_expiryYesCalendar days to expiry (above zero).
underlying_priceYesUnderlying price in dollars.
dividend_yield_pctYesDividend yield per year in percent (0 is allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the lower bar applies. The description adds real behavioral information beyond them: the tool may return a message rather than a number when the price has no implied volatility, and every input is mandatory with no defaults for rate or dividend yield.

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?

Two sentences, no filler, and the core definition of the computation is front-loaded before the input-requirement caveat. 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?

For a 7-parameter numerical solver with no output schema, the description covers the computational meaning, mandatory inputs, and the non-numeric failure outcome. Remaining gaps (result units, convergence behavior, handling of arbitrage-violating prices) are minor but real.

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 86%, so the schema already documents units (dollars, percent per year, calendar days) for each parameter, making 3 the baseline. The description only reinforces that rate_pct and dividend_yield_pct are required rather than optional, adding little semantics beyond the schema.

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 names the exact computation: the Black-Scholes volatility such that the model value equals a supplied option price. That is specific verb+resource and implicitly the inverse of the sibling black_scholes pricer, though it never names that sibling or states the contrast 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?

It states a hard precondition ('all inputs ... must be supplied') and warns that no volatility may fit, which helps the agent interpret a failure. But it does not say when to choose this over black_scholes or options_pnl_* tools; the inverse-pricing usage is only implied by the wording.

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