Skip to main content
Glama

curatedapi

Black-Scholes option price and Greeks calculator

calc_finance_black_scholes
Read-only

The Black-Scholes-Merton price of a European call or put with delta, gamma, vega, theta and rho, correct to the last digit shown.

Values a European option on a stock, index or currency with the Black-Scholes formula, with Merton's extension for a continuous dividend yield. The answer has the price and the five Greeks, and d1 and d2 for checking by hand. The normal distribution is evaluated with proven error bounds, so every digit returned is correct, including for options far in or out of the money where spreadsheet formulas lose digits.

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>",
      "strike": "<strike>",
      "time_to_expiry_years": "<time_to_expiry_years>",
      "volatility_percent": "<volatility_percent>",
      "risk_free_rate_percent": "<risk_free_rate_percent>",
      "option_type": "<option_type>"
    },
    "name": "calc_finance_black_scholes"
  }
}

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
volatility_percentYesVolatility per year in percent (20 for 20%). Allowed: > 0 and <= 1000. Unit: percent.
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 declare readOnly, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: Merton's continuous-dividend extension, inclusion of d1 and d2, and a numerical-accuracy guarantee via normal-CDF error bounds for deep in/out-of-the-money cases. It does not discuss rounding defaults, but the nested options object covers that.

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 a one-line summary of the exact outputs, followed by scope and accuracy claims. The accuracy paragraph is somewhat promotional ('spreadsheet formulas lose digits') but it carries informational value about numerical robustness, so it mostly earns its place.

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?

An output schema exists, so return values need not be spelled out, and the input schema is fully annotated. The description supplies the domain scope and accuracy guarantee an agent needs for a deterministic pricing calculator; only explicit alternative routing is missing.

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 already documents units (percent volatility and rates, years to expiry), ratio input syntax and bounds. The description only echoes a few of these semantics (continuous compounding of the dividend yield), so it adds little beyond the structured fields and 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?

The description names a specific model and output set: 'Black-Scholes-Merton price of a European call or put with delta, gamma, vega, theta and rho', and scopes the instrument class to stock, index or currency options. That distinguishes it in substance from calc_finance_black_76 (futures options) and calc_finance_implied_volatility (inverse problem), but it never names those siblings, so the differentiation must be inferred.

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?

Applicability is implied rather than stated: European exercise, stock/index/currency underlying, continuous dividend yield. There is no explicit when-to-use or when-not guidance, and no routing to calc_finance_black_76 for futures options or to the implied-volatility tool when the input is a market price rather than a volatility.

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