Skip to main content
Glama

Headroom Desk options calculators

Black-Scholes value and Greeks

black_scholes
Read-onlyIdempotent

Black-Scholes model value of one European-style call or put per share and per 100-share contract, with delta, gamma, theta per calendar day, vega per volatility point and rho per rate point. 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>",
      "underlying_price": "<underlying_price>",
      "strike": "<strike>",
      "days_to_expiry": "<days_to_expiry>",
      "volatility_pct": "<volatility_pct>",
      "rate_pct": "<rate_pct>",
      "dividend_yield_pct": "<dividend_yield_pct>"
    },
    "name": "black_scholes"
  }
}

Input Schema

NameRequiredDescriptionDefault
strikeYesStrike in dollars.
rate_pctYesInterest rate per year in percent (0 is allowed).
option_typeYes
days_to_expiryYesCalendar days to expiry (above zero).
volatility_pctYesVolatility per year in percent, for example 30.
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 bar is lower. The description still adds real substance: it fixes the units of each Greek (theta per calendar day, vega per volatility point, rho per rate point) and reports both per-share and per-100-share contract values, which annotations cannot convey.

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 dense sentences with zero filler, front-loaded with the model name and output set, followed by the input constraint. Every clause carries information about scope, units, or preconditions.

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 seven required parameters and no output schema, the description carries the return-value burden and discharges it by enumerating the value and all five Greeks with units. The only mild gap is not stating the exercise/style assumptions beyond 'European-style' or error behavior for bad inputs.

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 coverage is 86%, so the schema documents nearly every parameter including percent conventions and the zero-allowed cases. The description adds only that no inputs are optional, which the schema's required list already encodes; baseline 3 is appropriate.

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 a specific computation (Black-Scholes model value) plus the full Greek set, and constrains it to European-style calls or puts. It is clearly distinguishable from pricing-adjacent siblings like implied_volatility, though it never states that 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?

Usage is only implied: the tool computes a value when all pricing inputs are known. The sentence 'All inputs... must be supplied' sets a prerequisite but no when-to-use framing or routing away from alternatives such as implied_volatility or options_pnl_at_expiry is given.

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