Skip to main content
Glama

Headroom Desk options calculators

Options P/L before expiry (model estimate)

options_pnl_before_expiry
Read-onlyIdempotent

Black-Scholes model estimate of a position's P/L a given number of days from now at a given underlying price, for up to 8 legs. Each option leg needs its days to expiry and volatility. The interest rate and dividend yield must be supplied; nothing is built in.

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>",
      "underlying_price": "<underlying_price>",
      "days_from_now": "<days_from_now>",
      "rate_pct": "<rate_pct>",
      "dividend_yield_pct": "<dividend_yield_pct>"
    },
    "name": "options_pnl_before_expiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsYes
rate_pctYesInterest rate per year in percent, continuously compounded (0 is allowed).
days_from_nowYesCalendar days from now; not after any leg's expiry.
underlying_priceYesUnderlying price in dollars at which to value the position.
dividend_yield_pctYesDividend yield per year in percent, continuous (0 is allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond them: the result is a model estimate rather than market data, the 8-leg cap, and that interest rate and dividend yield have no defaults and must be supplied — a real failure mode an agent would otherwise hit. It stops short of saying how approximate or which pricing assumptions apply.

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, both front-loaded with the essential facts: what is computed, the scope limits, and the mandatory inputs. No filler or repetition of schema content.

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 calculator with a well-described schema and strong annotations, the description covers model basis, leg limits, and required inputs. The remaining gap is the return shape — with no output schema, the description never says whether the result is a single P/L figure, a per-leg breakdown, or includes Greeks.

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 80%, so the baseline is 3, but the description adds a non-obvious requirement: each option leg needs days_to_expiry and volatility_pct, which are not in the schema's per-leg required list (only type, side, quantity, price are). It also stresses that rate_pct and dividend_yield_pct are mandatory with nothing built in. It doesn't clarify units for underlying_price or how stock legs interact with the option pricing.

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?

States a specific computational verb (Black-Scholes model estimate) on a specific resource (a position's P/L), with the two scoping dimensions (days from now, underlying price) called out. It doesn't name the sibling options_pnl_at_expiry to draw the contrast, so an agent must infer the difference from 'before expiry' alone.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternative (options_pnl_at_expiry for expiry-date P/L, or black_scholes for single-option pricing). The only usage constraints given are implicit: up to 8 legs, and rate/dividend yield must be supplied by the caller.

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