Skip to main content
Glama

Headroom Desk options calculators

Covered call roll

covered_call_roll
Read-onlyIdempotent

Closing a written call and writing a new one: net credit or debit of the roll, total premium kept, new breakeven, return if called at the new strike with its per-year figures, highest and lowest P/L at the new 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_cost": "<share_cost>",
      "new_premium": "<new_premium>",
      "new_strike": "<new_strike>",
      "days_to_new_expiry": "<days_to_new_expiry>"
    },
    "name": "covered_call_roll"
  }
}

Input Schema

NameRequiredDescriptionDefault
contractsNo
new_strikeYesDollars per share, at most 4 decimals, for example "2.35".
share_costYesDollars per share, at most 4 decimals, for example "2.35".
new_premiumYesDollars per share, at most 4 decimals, for example "2.35".
cost_to_closeNoCost per share to close the current call (default 0).
days_to_new_expiryYes
premiums_received_so_farNoPremiums kept so far per share (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine value by enumerating the computed outputs (net credit/debit, total premium kept, new breakeven, per-year return if called, highest and lowest P/L), which is the real behavioral content for a pure calculator with no output schema.

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 the core operation front-loaded before the colon and no filler wording. The list that follows is dense but every item is a distinct output metric, so little is wasted; it is a fragment rather than a full sentence, which slightly weakens readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter calculator with no output schema, describing the returned metrics is the right instinct, but the description omits any mapping between the inputs (share cost, cost to close, premiums received so far) and those outputs, and never states the output format (report text vs. structured values). Adequate but with clear gaps an agent would have to probe for.

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 71%, so the schema carries most of the parameter documentation. The description only implicitly gestures at inputs through output phrases like 'total premium kept' and 'return if called at the new strike,' without mapping them to premiums_received_so_far or new_strike, and says nothing about contracts or days_to_new_expiry.

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 opens with a concrete definition of the operation: 'Closing a written call and writing a new one,' which identifies it as a roll computation and separates it from the plain covered_call sibling. It is clear what the tool computes, though it never explicitly names covered_call or states how the roll differs from evaluating a fresh position.

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 when-to-use or when-not-to-use guidance and no alternative is named among the siblings (covered_call, options_pnl_at_expiry, etc.). The prerequisite of already holding a written call is only inferable from the phrase 'closing a written call,' not stated as guidance.

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