Skip to main content
Glama

Headroom Desk options calculators

Covered call returns

covered_call
Read-onlyIdempotent

For 100 shares per contract with one call written against them: net debit, breakeven at expiry, return if called and if not called (each 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": {
      "share_price": "<share_price>",
      "call_strike": "<call_strike>",
      "premium": "<premium>",
      "days_to_expiry": "<days_to_expiry>"
    },
    "name": "covered_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
premiumYesPremium received per share.
contractsNo
call_strikeYesDollars per share, at most 4 decimals, for example "2.35".
share_priceYesDollars 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.6/5.0
Behavior3/5

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

Annotations already declare the operation read-only, idempotent, non-destructive and closed-world, and the description adds the modeling assumption of 100 shares per contract plus the exact set of output metrics. It does not disclose other behavioral assumptions that would affect results, such as day-count convention for annualization, dividends, or commissions.

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?

A single sentence with a colon-delimited list of outputs, front-loaded with the key position assumption. Every listed item corresponds to a real output, though the parenthetical '(each with its per-year figures)' is slightly awkward and could be tightened.

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 carries the burden of describing returns and does so by naming every metric produced, which is the essential information for an agent. Gaps remain around the annualization basis and output formatting, but the core is covered.

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?

The description adds real meaning beyond the schema: 'For 100 shares per contract with one call written against them' fixes the contract multiplier, which directly explains why the contracts parameter and the strike/premium per-share values interact the way they do, and 'at expiry' clarifies the horizon modeled by days_to_expiry. It stops short of documenting the annualization convention behind the per-year figures.

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 concretely enumerates what the tool computes for a covered call (net debit, breakeven, called/not-called returns, per-year figures, min/max P/L at expiry), so an agent can tell this is a covered-call return calculator rather than a roll or put tool. The only shortfall is that it uses a bare noun-phrase list rather than a verb stating the action, and it does not explicitly contrast with siblings like cash_secured_put.

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 by the position type in the name and the outputs listed; there is no explicit when-to-use statement, no prerequisites, and no routing to alternatives such as annualized_return despite this tool also reporting per-year figures. An agent can infer the context but must reason about 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