Skip to main content
Glama

Cash-secured put calculator

cash_secured_put
Read-onlyIdempotent

Cash-secured put figures: cash set aside, premium income, breakeven and effective purchase price if assigned, the discount to the stock price, return on the cash, maximum loss, and the model's chance of finishing above the breakeven when implied volatility and days are given.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDays to expiration, for the chance of profit. Optional.
priceYesStock price in dollars.
iv_pctNoImplied volatility, percent per year, for the chance of profit. Optional.
strikeYesThe strike of the put sold, in dollars.
premiumYesPremium received per share, in dollars.
contractsNoNumber of contracts, 100 shares each. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 and the description only needs to add computation context. It does add value by disclosing the full set of derived quantities, which is not visible in the annotations. However, it says nothing about units or conventions (percent vs. dollar for return on cash, annualized or not), the pricing/assignment assumptions behind 'effective purchase price if assigned,' or the model underlying the probability figure.

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 front-loaded sentence that leads with the resource and then lists outputs, with no filler or marketing language. The enumeration is dense but every item is a genuine return value rather than padding. Slightly long for a single sentence, though nothing could be cut without losing an output.

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?

There is no output schema, so the description carries the burden of describing return values, and it discharges that well by enumerating all eight derived figures. The schema is fully documented and the annotations cover the safety profile, so the remaining gap is minor: no units or sign conventions for ambiguous outputs such as 'return on the cash' and 'discount to the stock price,' and no statement of the pricing assumptions.

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 every parameter is already documented in the schema and the baseline is 3. The description adds modest meaning by tying implied volatility and days to a specific output (the chance of profit) and by implying that cash set aside derives from strike, premium, and contracts. It adds no syntax, unit, or default detail beyond what the schema already states.

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 specific resource (cash-secured put figures) and enumerates the exact outputs computed: cash set aside, premium income, breakeven, effective purchase price if assigned, discount, return on cash, max loss, and probability of finishing above breakeven. This is far more specific than a restatement of the title. It stops short of distinguishing itself from siblings like covered_call or profit_calculator, which an agent might reasonably confuse with a multi-output options calculator.

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?

There is no explicit when-to-use statement and no named alternative, so an agent must infer that this is the tool for evaluating a short put. The one piece of real guidance is the conditional clause 'when implied volatility and days are given,' which tells the agent that the probability output is gated on those optional inputs. That is useful but narrow; no prerequisites, exclusions, or sibling routing are 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