Skip to main content
Glama

BRAINIAC Options Analytics

Price an American option on a binomial tree

options-analytics_american-binomial-price
Read-onlyIdempotent

Price an American or European option on a Cox-Ross-Rubinstein tree with optional discrete cash dividends (escrowed method), and return tree delta, gamma, theta, the early-exercise boundary and the Black-Scholes-Merton European value for comparison. Price $0.04 USDC. POST /api/v1/options-analytics/american-binomial-price. 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_american-binomial-price"
  }
}

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.
stepsNosteps, integer, from 1 to 5000. Required.
styleNostyle, string, one of american, european. Required.american
strikeYesstrike, number. Required.
dividendsNodividends, array. Required.
timeYearsYestimeYears, number, from 0 to 50. Required.
dividendYieldNodividendYield, number, from -0.2 to 1. Required.

Output Schema

NameRequiredDescriptionDefault
deltaNodelta. Number.
gammaNogamma. Number.
modelNomodel. String.
priceNoprice. Number.
stepsNosteps. Number.
thetaNotheta. Number.
sourcesNosources. Array.
inputsUsedNoinputsUsed. Object.
convergenceNoconvergence. Object.
limitationsNolimitations. Array.
europeanPriceNoeuropeanPrice. Number.
earlyExerciseBoundaryNoearlyExerciseBoundary. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description discloses critical operational behavior: a $0.04 USDC cost, the POST endpoint, and that an unpaid call returns x402 payment terms without executing. That payment-gate behavior is not derivable from any structured field and prevents the agent from misreading a 402 response as a failure.

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?

The purpose is front-loaded with the verb 'Price', and the three sentences carry no filler. The first sentence is dense with output enumeration, but each item listed is material to the caller, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a ten-parameter numerical pricing tool with a full output schema and rich annotations, the description supplies the essentials: model, dividend convention, outputs, cost, endpoint, and payment-gate behavior. Return-value detail is correctly delegated to the output schema rather than duplicated.

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 all ten parameters, which sets the baseline at 3. The description adds only marginal meaning, clarifying that dividends are handled via the escrowed method and that a tree step count governs accuracy, but it does not explain the steps/accuracy tradeoff or the interaction of dividendYield with discrete dividends.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Price'), the instrument ('American or European option'), and the model ('Cox-Ross-Rubinstein tree'), plus the exact outputs (delta, gamma, theta, early-exercise boundary, BSM European comparison). This clearly separates it from sibling pricing/greeks tools such as black-scholes-greeks, which would not produce an early-exercise boundary.

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 mention of American exercise, discrete cash dividends, and a BSM European value for comparison hints at when this model is needed over a closed-form pricer. However, there is no explicit statement of when to choose this over siblings or when-not to use it, so the agent must infer routing.

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