Skip to main content
Glama

Headroom Desk options calculators

Cash-secured put returns

cash_secured_put
Read-onlyIdempotent

For a put written with cash set aside to take 100 shares per contract at the strike: cash secured, breakeven and cost per share if assigned, return on the cash with its per-year figures, highest and lowest P/L at expiry.

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": {
      "put_strike": "<put_strike>",
      "premium": "<premium>",
      "days_to_expiry": "<days_to_expiry>"
    },
    "name": "cash_secured_put"
  }
}

Input Schema

NameRequiredDescriptionDefault
premiumYesPremium received per share.
contractsNo
put_strikeYesDollars per share, at most 4 decimals, for example "2.35".
days_to_expiryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without description help. What the description adds is the return surface: it tells the agent which figures come back, which matters because there is no output schema. It says nothing about units or rounding of the returned values or whether P/L figures assume assignment.

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?

One dense sentence that front-loads the scenario and then lists outputs in a compact chain. Nothing is redundant, though the colon-and-commas construction makes it slightly harder to parse than separate sentences would.

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 no output schema, the description correctly spends its budget enumerating return values, which is the main gap it needed to fill. The 100-shares-per-contract assumption and expiration P/L extrema are covered; minor gaps remain on output units and on the two undocumented parameters.

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 50%: premium and put_strike are documented in the schema, while contracts and days_to_expiry are not. The description partially compensates — '100 shares per contract' clarifies the contracts multiplier and 'per-year figures' implies annualization of days_to_expiry — but both remain implicit rather than stated.

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 the exact computation — cash-secured put returns — and enumerates the specific outputs (cash secured, breakeven, cost per share if assigned, return on cash with annualized figures, highest/lowest P/L at expiry). That is enough to distinguish it from siblings like options_pnl_at_expiry or annualized_return, though it never states the verb ('computes') and the scenario framing takes a clause to unpack.

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 opening clause implies the use case (a put written with cash set aside to take 100 shares per contract), so an agent can infer when this applies. There is no explicit when-to-use versus alternatives, no mention of the covered_call or options_pnl siblings, and no stated exclusions.

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