Skip to main content
Glama

BRAINIAC Options Analytics

Compute multi-leg option strategy payoff

options-analytics_strategy-payoff
Read-onlyIdempotent

Compute payoff and profit or loss of a multi-leg option and stock position at expiry and at a valuation date, with exact breakevens, maximum profit and loss, and unlimited-risk flags. Price $0.03 USDC. POST /api/v1/options-analytics/strategy-payoff. 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": {
      "spot": "<spot>",
      "legs": "<legs>"
    },
    "name": "options-analytics_strategy-payoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridNogrid, object. Optional.
legsYeslegs, array. Required.
rateNorate, number, from -0.2 to 1. Required.
spotYesspot, number. Required.
multiplierNomultiplier, number. Required.
dividendYieldNodividendYield, number, from -0.2 to 1. Required.
valuationTimeYearsNovaluationTimeYears, value. Optional.

Output Schema

NameRequiredDescriptionDefault
gridNogrid. Array.
modelNomodel. String.
maxLossNomaxLoss. Number.
sourcesNosources. Array.
maxProfitNomaxProfit. Number.
breakevensNobreakevens. Array.
inputsUsedNoinputsUsed. Object.
netPremiumNonetPremium. Number.
limitationsNolimitations. Array.
unlimitedLossNounlimitedLoss. Boolean.
unlimitedProfitNounlimitedProfit. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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), and the description adds genuinely new context: a fixed $0.03 USDC charge and the failure mode that an unpaid call returns x402 payment terms without executing. That payment/auth disclosure is valuable beyond the annotations, though rate limits, latency, or determinism of grid results are not discussed.

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 the capability and its outputs, followed by price, endpoint, and the payment failure behavior — all short and purposeful. The raw endpoint path adds little for an agent but is a minor cost, and the sentence ordering is sensible.

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 tool with nested objects and a 100% documented schema plus an output schema, the description supplies what the structured fields cannot: cost and the x402 payment requirement. Nothing essential to correct invocation is missing, though comparative guidance against sibling analytics tools would make it fully complete.

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 all seven parameters (including the nested legs and grid objects) are already documented in the schema. The description adds no meaning about units, defaults, or how legs are interpreted beyond what the schema states, which is the expected baseline when the schema carries the burden.

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?

States a specific verb and resource ('Compute payoff and profit or loss of a multi-leg option and stock position') plus the scope ('at expiry and at a valuation date') and the concrete outputs (breakevens, max profit/loss, unlimited-risk flags). This clearly separates it from pricing/greeks/IV siblings such as options-analytics_black-scholes-greeks without needing to name them.

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 implied by the scope: an agent can infer it should call this for expiry/valuation payoff analysis of multi-leg positions. However, there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. probability-of-profit or position-greeks-aggregate for different questions), and no prerequisites stated.

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