Skip to main content
Glama

Covered call calculator

covered_call
Read-onlyIdempotent

Covered call figures for shares already held: premium income, breakeven, maximum profit if the shares are called away, the return if the stock is unchanged and the downside cushion, each for the length of the trade. Says when the strike is below the cost basis, and when no stock price breaks even.

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>",
      "strike": "<strike>",
      "premium": "<premium>"
    },
    "name": "covered_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesStock price in dollars.
strikeYesThe strike of the call sold, in dollars.
premiumYesPremium received per share, in dollars.
contractsNoNumber of contracts, 100 shares each. Default 1.
cost_basisNoWhat the shares cost per share, in dollars. Defaults to the stock price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / days
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "maximum": 3650,
      -      "type": "number"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Days to expiration, for the simple annualized figure (shown from 7 days up). Optional.",
      -  "title": "Days"
      -}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral context the annotations cannot: which metrics are returned and that the tool flags the strike-below-cost-basis case and the no-breakeven case. It omits nothing critical for a pure calculator.

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?

Outputs are front-loaded in one dense sentence, followed by a short note on edge cases; little is wasted. The second fragment ('Says when...') is slightly informal but still earns its place by flagging special-case warnings.

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 explaining return values and does so by enumerating all five metrics, plus the two special-case warnings. Parameters are fully covered by the schema, so the only residual gap is the ambiguous 'length of the trade' phrasing.

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 100%, so price, strike, premium, contracts and cost_basis are already well documented, and the description adds no parameter-level detail. The phrase 'each for the length of the trade' is slightly confusing because no expiry or duration parameter exists in the schema, which could mislead an agent looking for a time input.

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 resource (covered call figures) and enumerates the exact outputs: premium income, breakeven, max profit if called away, return if unchanged, downside cushion. 'For shares already held' implicitly distinguishes it from the cash_secured_put sibling, but no alternative is named explicitly.

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?

The precondition 'for shares already held' implies when the tool applies, and 'strike below the cost basis' hints at an edge case. However, there is no explicit when-to-use guidance and no statement routing the agent to profit_calculator, cash_secured_put, or what_if instead.

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