Skip to main content
Glama

Headroom Desk options calculators

Options P/L at expiry

options_pnl_at_expiry
Read-onlyIdempotent

Exact P/L at expiry for a position of up to 8 legs (calls, puts, shares, long or short): net premium (debit or credit), breakevens, highest and lowest P/L at expiry (or Unlimited), and the P/L at each strike and at any underlying prices given. Covers spreads, straddles, strangles, iron condors, butterflies, covered calls and collars. Uses only the numbers supplied.

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": {
      "legs": "<legs>"
    },
    "name": "options_pnl_at_expiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsYes
prices_at_expiryNoOptional underlying prices at expiry to evaluate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a safe, deterministic, read-only calculation. The description adds useful context beyond them: it accepts up to 8 legs, covers common strategies, returns key expiry metrics, and emphasizes that it uses only supplied numbers rather than live market data.

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?

The description is front-loaded with the core purpose and is appropriately sized for a calculator tool. The output list and strategy examples earn their place by helping an agent recognize coverage without excessive detail.

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 tool with no output schema, the description adequately enumerates the main return values and the 8-leg limit. It could say more about response shape or edge cases, but the annotations and schema cover most remaining operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Most parameter meaning comes from the input schema, which describes price, strike, quantity, multiplier, and prices_at_expiry. The description largely repeats schema facts such as the 8-leg maximum and the allowed leg types/sides, without compensating for the 50% schema description coverage.

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?

The description states a specific calculation: exact P/L at expiry for an options/stock position of up to 8 legs. It names the returned components (net premium, breakevens, highest/lowest P/L, per-strike and per-underlying P/L) and is naturally distinguishable from the sibling before-expiry tool.

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 by 'at expiry' and the strategy list, which helps an agent recognize when this calculator applies. However, the description does not explicitly compare it with options_pnl_before_expiry or state when not to use it.

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