Skip to main content
Glama
Sign In

TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures

by io.github.SKalinin909
OverviewDiscussionsAdmin

Cash Secured Put

workflow.run_cash_secured_put
Read-only

Cash-secured put on a US stock or ETF, in US dollars with the standard 100-share contract (NOT Deribit and not coin-settled): you sell puts and hold the cash to buy the shares if they are assigned. Returns the premium income, the cash held as collateral (strike x 100 x contracts), the return for the period (premium / collateral) and the simple annualized return by days to expiry (365-day year, not compounded), the effective buy price if assigned (strike minus premium, which is also the breakeven), the net cost of the shares if assigned, the maximum profit (the premium), the maximum loss (shares to zero) and the dollars lost per $1 the price falls below the breakeven. Optional spotPrice adds the discount to buying the shares now and the strike distance from the spot; optional scenarioPrice adds the P&L at expiry at that price, whether the put is assigned, and the same price move compared with buying the shares now at spotPrice. A scenario price exactly at the strike counts as not assigned (the P&L is the same either way). A premium at or above the strike is refused. The premium is the one you type (per share, as quoted); commissions, early assignment, taxes, dividends and interest on the cash are not modelled. Edge cases: strike above zero; premium 0 or more and below the strike; contracts a whole number from 1 to 1,000,000; daysToExpiry 1 to 3650; spotPrice above zero and scenarioPrice 0 or more when given. Not covered: a fractional contract, and (already stated) commissions, early assignment, taxes, dividends and interest on the cash. Use when the user asks what selling a cash-secured put pays, what price they would effectively buy at, or whether it beats buying the stock now. Prices are computed, nothing is fetched.

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": {
      "strike": "<strike>",
      "premium": "<premium>",
      "contracts": "<contracts>",
      "daysToExpiry": "<daysToExpiry>"
    },
    "name": "workflow.run_cash_secured_put"
  }
}

Input Schema

NameRequiredDescriptionDefault
strikeYesStrike price of the put, USD per share, above 0
premiumYesPremium received per share as quoted, USD, 0 or more and below the strike. A contract covers 100 shares, so 2.50 pays 250 dollars per contract.
contractsYesNumber of contracts sold, a whole number from 1 to 1,000,000
spotPriceNoOptional: the share price today, USD, above 0, for the comparison with buying now
daysToExpiryYesCalendar days to expiry, 1 to 3650
scenarioPriceNoOptional: a share price at expiry, USD, 0 or more, to report the P&L at

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses that a premium at or above the strike is refused, that a scenario price exactly at the strike counts as not assigned, what is deliberately not modelled (commissions, early assignment, taxes, dividends, cash interest), and that 'Prices are computed, nothing is fetched.' This is the behavioral context an agent needs beyond the safety hints.

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?

Purpose and constraints are front-loaded, and the output enumeration is dense and informative. Slightly long and run-on, with a mild redundancy ('Not covered: a fractional contract, and (already stated) commissions...') acknowledging prior text, but almost every sentence carries information.

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?

No output schema exists, and the description fully enumerates every returned value (premium, collateral, period return, annualized return, effective buy price/breakeven, net cost, max profit/loss, dollars lost per $1 fall) plus validation bounds. Complete for a computation tool of this complexity.

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 baseline is 3, but the description adds real meaning: premium is per-share as quoted with a 100-share multiplier, spotPrice adds discount-to-spot and strike distance, scenarioPrice adds expiry P&L and assignment status, and the derived outputs (collateral = strike x 100 x contracts). Adds value over the schema's field-level docs.

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 product (cash-secured put on a US stock/ETF, USD, standard 100-share contract) and explicitly excludes the conflicting sibling family by noting it is 'NOT Deribit and not coin-settled.' An agent can distinguish it from run_covered_call_protective_put or options payoff tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives three concrete when-to-use triggers: what the put pays, the effective buy price, and whether it beats buying the stock now. It also states scope exclusions (not Deribit/coin-settled, not fractional contracts). It does not explicitly name the closest sibling alternative, so not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources