Skip to main content
Glama

BRAINIAC Options Analytics

Check put-call parity and implied forward

options-analytics_put-call-parity-check
Read-onlyIdempotent

Infer the implied forward and carry from call and put quote pairs, solve the rate by least squares when omitted, and flag pairs whose bid and ask break the European or American parity band. Price $0.03 USDC. POST /api/v1/options-analytics/put-call-parity-check. 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>",
      "timeYears": "<timeYears>",
      "pairs": "<pairs>"
    },
    "name": "options-analytics_put-call-parity-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNorate, value. Optional.
spotYesspot, number. Required.
pairsYespairs, array. Required.
styleNostyle, string, one of european, american. Required.european
timeYearsYestimeYears, number, from any to 50. Required.
toleranceAbsNotoleranceAbs, number, from 0 to any. Required.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
pairsNopairs. Array.
sourcesNosources. Array.
inputsUsedNoinputsUsed. Object.
impliedRateNoimpliedRate. Null.
limitationsNolimitations. Array.
impliedCarryNoimpliedCarry. Number.
impliedForwardNoimpliedForward. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: the endpoint is POST, the call costs $0.03 USDC, and an unpaid call returns x402 payment terms without executing. That is real operational disclosure beyond the annotations; it stops short of 5 because it says nothing about failure modes such as malformed pairs or invalid rate inputs.

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 tight sentences, front-loaded with the operation before pricing and transport details. Every clause carries information; the only mild redundancy is restating the endpoint path alongside the operation name.

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?

With annotations, a full input schema and an output schema, the description supplies what structured fields cannot: pricing, the x402 failure behavior, and the least-squares fallback for rate. The remaining gap is that the style parameter's practical effect (which parity band applies) is stated but not elaborated, and date/units assumptions for timeYears are left to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the 3 baseline is already met, yet the description adds meaning the schema cannot convey: rate is optional and is solved by least squares when omitted, and style selects which parity band (European or American) is enforced. toleranceAbs is only indirectly implied by 'flag pairs whose bid and ask break the band', so the parameter story is not complete.

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 concrete verb and resource: infer the implied forward and carry from call/put quote pairs, solve the rate by least squares, and flag parity-band violations. That is far more specific than the title alone and is clearly distinct from siblings such as implied-volatility-solve or black-scholes-greeks. It does not explicitly name a sibling to contrast with, so it falls short of a 5.

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?

The description implies when the tool applies (paired call and put quotes at the same strike) and explains the 'rate omitted' path, which is useful routing information. But it gives no when-not-to-use guidance and never contrasts itself with the nearby pricing or volatility tools that an agent might otherwise choose.

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