Skip to main content
Glama

Iron condor calculator

iron_condor
Read-onlyIdempotent

Iron condor figures from the four strikes and the net credit: both wing widths, maximum profit and loss, both breakevens, return on risk, credit-to-width, and the model's chance of profit when implied volatility and days are given. A side the credit covers in full has no breakeven, and the answer says so.

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>",
      "long_put_strike": "<long_put_strike>",
      "short_put_strike": "<short_put_strike>",
      "short_call_strike": "<short_call_strike>",
      "long_call_strike": "<long_call_strike>",
      "credit": "<credit>"
    },
    "name": "iron_condor"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays to expiration, for the chance of profit. Optional.
priceYesStock price in dollars.
creditYesTotal net credit received per share for the four legs, in dollars.
iv_pctNoImplied volatility, percent per year, for the chance of profit. Optional.
contractsNoNumber of contracts. Default 1.
long_put_strikeYesThe strike of the put bought, the lowest of the four, in dollars.
long_call_strikeYesThe strike of the call bought, the highest of the four, in dollars.
short_put_strikeYesThe strike of the put sold, in dollars.
short_call_strikeYesThe strike of the call sold, in dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real behavioral value by disclosing the edge case that a fully credit-covered side has no breakeven and that the response reports this. It does not say how contracts affect the magnitude of profit/loss figures, which is the main behavioral gap.

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?

Two sentences, front-loaded with the computed outputs and ending on the most valuable edge-case note. No filler, no repetition of the title, and every clause carries information.

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?

For a read-only, no-output-schema tool with 9 fully documented parameters, the description covers the return shape well enough to pick and call it. The remaining gap is how the contracts parameter scales the profit/loss and return-on-risk figures, which matters for correct interpretation of the answer.

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 every parameter including units, defaults, and max bounds is already documented in the schema. The description only loosely maps the required inputs ('four strikes and the net credit') and says nothing about the contracts multiplier's effect on outputs, so it adds little beyond the structured data. Baseline 3 applies.

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 resource (iron condor) and enumerates the concrete outputs: wing widths, max profit/loss, breakevens, return on risk, credit-to-width, chance of profit. That is far more specific than a title restatement, but it never contrasts itself with overlapping siblings like profit_calculator or credit_spread, so an agent must infer which calculator to use.

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 only implied: the opening phrase 'from the four strikes and the net credit' signals which inputs are needed, and 'when implied volatility and days are given' implies the optional path for chance of profit. There is no explicit when-to-use, when-not-to-use, or named alternative anywhere in the description.

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