Skip to main content
Glama

BRAINIAC Options Analytics

Compute lognormal option probabilities

options-analytics_probability-of-profit
Read-onlyIdempotent

Compute lognormal probabilities of finishing above or below levels, touching a level before expiry, and finishing in profit for a strategy given its breakevens, under risk-neutral or real-world drift. Price $0.02 USDC. POST /api/v1/options-analytics/probability-of-profit. 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>",
      "sigma": "<sigma>",
      "timeYears": "<timeYears>"
    },
    "name": "options-analytics_probability-of-profit"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNorate, number, from -0.2 to 1. Required.
spotYesspot, number. Required.
driftNodrift, value. Optional.
sigmaYessigma, number, from any to 5. Required.
levelsNolevels, array. Required.
measureNomeasure, string, one of risk_neutral, real_world. Required.risk_neutral
timeYearsYestimeYears, number, from any to 50. Required.
breakevensNobreakevens, array. Optional.
profitAboveNoprofitAbove, boolean. Optional.
dividendYieldNodividendYield, number, from -0.2 to 1. Required.
profitBetweenNoprofitBetween, array. Optional.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
levelsNolevels. Array.
sourcesNosources. Array.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.
probabilityOfProfitNoprobabilityOfProfit. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 non-obvious operational context: a $0.02 USDC cost, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. That payment-gate behavior is the key thing an agent must know before calling and is not in any structured field. It stops short of describing rate limits or retry semantics.

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 statement is front-loaded and dense with specifics, followed by operational facts in short sentences. No filler, though the endpoint path and price could be split or trimmed if space were at a premium.

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 an 11-parameter tool with full schema coverage and an existing output schema, the description supplies what structured data cannot: what the computation yields conceptually, the drift/measure semantics, and the payment workflow. Return-value detail is correctly left to the output schema.

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 11 parameters, making 3 the baseline. The description adds some conceptual framing by tying breakevens to the profit outputs and mentioning the risk-neutral vs real-world drift switch, but it says nothing about how levels, profitAbove, profitBetween, or the array pair interact to select which probabilities are returned.

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 (compute) and enumerates the exact quantities produced: probability of finishing above/below levels, of touching a level before expiry, and of finishing in profit from breakevens. That is clearly distinguishable from sibling pricing/Greeks/volatility tools without opening any schema.

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?

It implicitly tells the agent this is the probability tool (as opposed to a pricing or greeks tool), but never states when to choose it over siblings like expected-move or strategy-payoff, nor any prerequisites or exclusions. A usage context is inferable from the enumerated outputs rather than 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