Skip to main content
Glama
Sign In

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Analyze Option Strategy

AnalyzeOptionStrategy
Read-only

Work out the arithmetic of one to four proposed option legs: net debit or credit, payoff, breakevens and whole-position greeks. Long legs price at the ask and short legs at the bid; a leg without a usable quote falls back to its last trade, and the answer then says the result cannot be executed at. Legs in one expiration give a terminal payoff; legs in two give one result per path, since the back legs still carry time value at the front expiration. This is reference arithmetic, not a recommendation, and it states no probability of profit. Plus reads delayed indicative quotes, Pro real-time; the Free plan is answered with an upgrade note. US tickers only.

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

Input Schema

NameRequiredDescriptionDefault
legsYesOne to four legs, each an OCC symbol, a side (long or short) and a quantity
tickerYesUS stock ticker, e.g. AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnly, non-destructive, closed-world; the description adds substantial behavior: long legs price at the ask and short at the bid, a leg without a usable quote falls back to last trade and the result is flagged as unexecutable at, and two-expiration positions return one result per path because back legs retain time value. It also discloses data freshness by tier (delayed indicative versus real-time) and the free-plan refusal path.

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?

The purpose is front-loaded in the first clause and every subsequent sentence adds a distinct, load-bearing fact — pricing rule, quote fallback, expiration branching, disclaimer, data tiering, geography. The sentences are long and multi-clause, which slightly taxes scanning, but there is no filler to cut.

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 must convey what comes back, and it does: debit/credit, payoff, breakevens, greeks, and the per-path shape for two expirations, plus the unexecutable-price flag. Remaining gaps are minor — no statement of what a partially quoted or ambiguous leg does beyond the last-trade fallback, and no indication of the response size for a four-leg strategy.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains the leg count limit, why legs may span one or two expirations and what that changes, and that side determines the pricing side. Quantity semantics and the OCC-symbol sourcing are left to the schema, which already documents them.

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 opens with a specific verb and resource — 'Work out the arithmetic of one to four proposed option legs' — then enumerates the exact outputs: net debit or credit, payoff, breakevens, and whole-position greeks. This clearly separates it from quote-fetching siblings like GetOptionChain or GetOptionContract, which supply the inputs rather than evaluating a position.

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

Usage Guidelines4/5

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

It states scope conditions well: one to four legs, US tickers only, one versus two expirations, and plan gating (Free plan returns an upgrade note). It also sets expectations that this is reference arithmetic and not a recommendation. It does not name a sibling alternative for the case where the agent lacks an OCC symbol, but the usage context is otherwise clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Equibles toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources