Skip to main content
Glama

TipRanks

by com.tipranks
OverviewDiscussions(1)Admin

get_options_chain

Read-onlyIdempotent

Contracts at one expiration, enriched with price + OI + volume.

Each row: ticker (OCC), contract_type, strike, name, price, volume,
open_interest, open_interest_change, change_percent, day_open / high /
low, last_trade_date.

Quotes are typically delayed ~15 minutes. Greeks and implied
volatility are NOT exposed by this data source — do not fabricate
them.

Args:
    ticker: Underlying (e.g. 'AAPL').
    expiration_date: One of the dates from get_options_expirations
        (YYYY-MM-DD).
    contract_type: '' for both, or 'call' or 'put'.
    strike_gte: Filter strikes >= this value (optional).
    strike_lte: Filter strikes <= this value (optional).
    limit: Max contracts to return (default 50).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
tickerYes
strike_gteNo
strike_lteNo
contract_typeNo'call' or 'put'; omit to return both sides.
expiration_dateYesExact expiration in YYYY-MM-DD. REQUIRED — call get_options_expirations first to discover valid dates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_options_chainOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the description adds value by disclosing the ~15-minute quote delay, the absence of Greeks/IV in the data source, and the exact list of returned row fields. This is rich behavioral context beyond the structured metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: a one-line purpose, a compact output field list, a behavior note, and a clear Args block. Every sentence adds necessary information, with no filler or repetition. It is appropriately sized for a six-parameter tool.

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?

With no output schema, the description enumerates all return fields, covering price, volume, OI, and price range. It also provides usage context (expiration discovery), data timing (delayed quotes), and limitation warnings. The combination of annotations and description fully equips an agent to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite schema description coverage of only 33%, the description's Args section fully explains all six parameters with examples ('AAPL'), constraints (strike filters, limit default 50), and the requirement that expiration_date comes from get_options_expirations. It more than compensates for the schema's gaps.

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 first sentence 'Contracts at one expiration, enriched with price + OI + volume' states a specific verb (get) and resource (option chain for one expiration). It clearly distinguishes from get_options_expirations (dates only) and get_options_contract (single contract) by emphasizing a full chain at a single expiration.

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

Usage Guidelines5/5

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

Explicitly instructs to use get_options_expirations first to discover valid expiration dates, and warns that Greeks/IV are not available and must not be fabricated. This gives clear when-to-use and what-not-to-use guidance, plus a direct reference to a sibling tool.

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

All TipRanks 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