Skip to main content
Glama
Sign In

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Option Term Structure

GetOptionTermStructure
Read-only

Compare the nearest upcoming expirations side by side: at-the-money implied volatility, the at-the-money straddle's mid as a market-implied expected move, put/call ratios and max pain for each. An expiration that could not be read stays in the table, marked. Nothing here is a forecast. 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>"
    },
    "name": "GetOptionTermStructure"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesUS stock ticker, e.g. AAPL
maxExpirationsNoExpirations to compare (default: 8, max: 12)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile, and the description adds real behavior beyond them: unreadable expirations remain in the table marked rather than erroring, quotes are delayed indicative on Plus versus real-time on Pro, the Free plan returns an upgrade note rather than a failure, and results are explicitly not a forecast. That partial-failure and tier-gating disclosure is exactly what an agent needs to avoid misinterpreting an answer.

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?

Front-loaded with the comparison itself, then caveats, then access tiers and market scope, with no wasted sentences. The phrasing is slightly telegraphic ('Plus reads delayed indicative quotes, Pro real-time'), which costs a little clarity but keeps the definition compact.

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

Completeness5/5

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

For a two-parameter read-only tool with no output schema, the description covers the returned table's contents, how partial failures are surfaced, quote freshness by plan, and the US-only restriction. Nothing an agent needs in order to call it or interpret its output is missing.

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% and both parameters, including the default of 8 and max of 12 on maxExpirations, are documented in the schema. The description implies the row count corresponds to compared expirations but adds no format or edge-case detail beyond what the schema already states, so the baseline of 3 applies.

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?

States a specific verb and resource ('Compare the nearest upcoming expirations side by side') and enumerates exactly what is compared: ATM implied volatility, ATM straddle mid as expected move, put/call ratios, max pain. That enumeration distinguishes it from siblings like GetOptionExpirations (a list) and GetPutCallRatios (a single metric).

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?

The comparative framing plus 'nearest upcoming expirations' and 'US tickers only' gives clear context for when this tool is the right pick over a full chain pull. It does not explicitly name an alternative such as GetOptionChain for deeper per-strike work, so routing between option tools still requires inference from the names.

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