Skip to main content
Glama

BRAINIAC Options Analytics

Price a European option and its Greeks

options-analytics_black-scholes-greeks
Read-onlyIdempotent

Price a European option with Black-Scholes-Merton and return delta, gamma, vega, theta, rho, vanna and charm from caller-supplied spot, strike, time, rate, dividend yield and volatility. Pure computation with a high-accuracy normal CDF. Price $0.02 USDC. POST /api/v1/options-analytics/black-scholes-greeks. 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": {
      "type": "<type>",
      "spot": "<spot>",
      "strike": "<strike>",
      "timeYears": "<timeYears>",
      "sigma": "<sigma>"
    },
    "name": "options-analytics_black-scholes-greeks"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNorate, number, from -0.2 to 1. Required.
spotYesspot, number. Required.
typeYestype, string, one of call, put. Required.
sigmaYessigma, number, from any to 5. Required.
greeksNogreeks, array. Required.
strikeYesstrike, number. Required.
dayCountNodayCount, string, one of ACT/365, ACT/360, TRADING/252. Required.ACT/365
timeYearsYestimeYears, number, from 0 to 50. Required.
dividendYieldNodividendYield, number, from -0.2 to 1. Required.

Output Schema

NameRequiredDescriptionDefault
d1Nod1. Number.
d2Nod2. Number.
rhoNorho. Number.
vegaNovega. Number.
charmNocharm. Number.
deltaNodelta. Number.
gammaNogamma. Number.
modelNomodel. String.
priceNoprice. Number.
thetaNotheta. Number.
vannaNovanna. Number.
sourcesNosources. Array.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.
thetaPerDayNothetaPerDay. Number.
vegaPer1PctNovegaPer1Pct. Number.

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, idempotent, non-destructive and open-world. The description adds real value beyond them: the price ($0.02 USDC), the x402 payment gate and the fact that an unpaid call does not execute, plus the claim of a pure, high-accuracy computation. It doesn't cover error shapes or timeYears=0 edge behavior.

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?

Three sentences, front-loaded with the core action and output list, followed by cost and payment behavior. No filler; only lightly repetitive with the title's pricing framing.

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?

Output schema exists, so the description needn't explain return values, and it covers cost, transport, and payment failure mode. For a 9-parameter computational tool the remaining gaps (day-count convention meaning, behavior at zero time to expiry) are minor.

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 parameters and their enum values are already documented. The description lists the input set (spot, strike, time, rate, dividend yield, volatility) and the optional greeks selection channel, but adds no units, conventions, or dayCount semantics beyond what the schema carries.

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+resource ('Price a European option with Black-Scholes-Merton') and enumerates the returned Greeks. The 'European' plus 'Black-Scholes-Merton' framing implicitly separates it from the American binomial sibling, but it never names that alternative, so the differentiation is left for the agent to infer.

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 (closed-form European pricing from caller-supplied inputs) and the note about unpaid calls returning x402 terms is useful operational guidance. There is no explicit when-to-use vs. when-not guidance relative to the binomial or IV-solve siblings.

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