Skip to main content
Glama

BRAINIAC Options Analytics

Compute covered call and cash-secured put yield

options-analytics_covered-call-yield
Read-onlyIdempotent

Compute static and if-called returns, annualised returns, downside protection and breakeven for a covered call, or the return on collateral for a cash-secured put. Price $0.02 USDC. POST /api/v1/options-analytics/covered-call-yield. 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": {
      "strategy": "<strategy>",
      "strike": "<strike>",
      "premium": "<premium>",
      "daysToExpiry": "<daysToExpiry>"
    },
    "name": "options-analytics_covered-call-yield"
  }
}

Input Schema

NameRequiredDescriptionDefault
strikeYesstrike, number. Required.
premiumYespremium, number. Required.
strategyYesstrategy, string, one of covered_call, cash_secured_put. Required.
commissionNocommission, number, from 0 to any. Required.
stockPriceNostockPrice, number. Optional.
daysToExpiryYesdaysToExpiry, integer, from 1 to 1095. Required.
dividendsBeforeExpiryNodividendsBeforeExpiry, number, from 0 to any. Required.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
sourcesNosources. Array.
netDebitNonetDebit. Number.
strategyNostrategy. String.
breakevenNobreakeven. Number.
collateralNocollateral. Null.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.
staticReturnNostaticReturn. Number.
ifCalledReturnNoifCalledReturn. Number.
staticAnnualizedNostaticAnnualized. Number.
compoundAnnualizedNocompoundAnnualized. Number.
downsideProtectionNodownsideProtection. Number.
ifCalledAnnualizedNoifCalledAnnualized. Number.
ifCalledCompoundAnnualizedNoifCalledCompoundAnnualized. 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 read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond them: a $0.02 USDC price and the fact that an unpaid call returns x402 payment terms without executing. It stops short of saying how optional inputs like stockPrice or dividends alter results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the computed outputs, followed by cost and the payment gate. No filler or restatement of the title.

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?

An output schema exists, so return values needn't be enumerated, and the description still names the headline metrics plus the payment failure mode. The only real gap is the role of optional inputs such as stockPrice and dividends in a 7-parameter tool.

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 coverage is 100%, so each parameter is already documented, and the description adds no per-parameter meaning (e.g. what happens if the optional stockPrice is omitted for a covered call). Baseline 3 is appropriate when the schema does the heavy lifting.

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 computation ('static and if-called returns, annualised returns, downside protection and breakeven') for two named strategy types, plus the endpoint path. This clearly separates it from sibling pricing/Greek tools like strategy-payoff or black-scholes-greeks.

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 rather than stated: the description makes clear the tool is for covered call / cash-secured put yield analysis, but never says when to prefer it over siblings such as strategy-payoff or probability-of-profit, nor what prerequisites (e.g. needing a spot price) apply.

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