Skip to main content
Glama
Sign In

ApexTick Market Data & Options MCP

by com.apextick.api
OverviewDiscussionsAdmin

get_options_chain

Read-onlyIdempotent

Option chain, expiration dates, historical option contract bars, and Black-Scholes Greeks lookup for a single underlying ticker: returns available expiration dates and liquid call/put contracts with strike, bid, ask, implied volatility, volume, open interest and Greeks (delta, gamma, theta, vega, rho). When strike is also provided (with expiration and option_type call/put), returns historical daily OHLCV, open interest, implied volatility and Black-Scholes Greeks for that active or expired option contract.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_options_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional end date in YYYY-MM-DD format when strike is specified for historical option bars
fromNoOptional start date in YYYY-MM-DD format when strike is specified for historical option bars
limitNoMaximum number of option contracts or historical daily bars to return, 1-50 (default 10 for chains, 30 for historical bars)
strikeNoOptional strike price (e.g. 200 or 345) to retrieve historical daily OHLCV, Open Interest, Implied Volatility and Black-Scholes Greeks for a specific active or expired option contract (requires expiration and option_type call or put)
symbolYesUnderlying equity or ETF ticker in standard market notation, e.g. AAPL, NVDA, SPY, QQQ
expirationNoOptional expiration date filter in YYYY-MM-DD format (e.g. 2026-11-20). Required when strike is specified for historical contract bars
option_typeNoOptional contract type filter: all (default: both calls and puts), call or put

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / expiration / description
      Previous value: -"Optional expiration date filter in YYYY-MM-DD format (e.g. 2026-11-20). Omit to return available expiration dates and the most liquid near-the-money contracts across upcoming expiries"New value: +"Optional expiration date filter in YYYY-MM-DD format (e.g. 2026-11-20). Required when strike is specified for historical contract bars"
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Optional start date in YYYY-MM-DD format when strike is specified for historical option bars",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of option contracts to return, 1-50 (default 10, ranked by liquidity and proximity to the underlying price)"New value: +"Maximum number of option contracts or historical daily bars to return, 1-50 (default 10 for chains, 30 for historical bars)"
    • addedInput schema / properties / strike
      Added value: +{
+  "description": "Optional strike price (e.g. 200 or 345) to retrieve historical daily OHLCV, Open Interest, Implied Volatility and Black-Scholes Greeks for a specific active or expired option contract (requires expiration and option_type call or put)",
+  "type": "number"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Optional end date in YYYY-MM-DD format when strike is specified for historical option bars",
+  "type": "string"
+}
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description earns credit for enumerating the returned fields (strike, bid, ask, IV, volume, open interest, Greeks) and noting Greeks are Black-Scholes, but it says nothing about data freshness, rate limits, or how an expired contract behaves versus an active one beyond 'active or expired'.

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?

Two sentences, front-loaded with the chain mode and then the historical mode, with no filler. It is somewhat dense and repeats the Greeks list in both sentences, which is minor redundancy rather than wasted space.

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?

There is no output schema, so the description must carry the return-shape burden, and it does by naming the fields each mode returns. A mutation-free read tool with fully documented parameters needs little more, though a note on ordering or which expirations are 'liquid' would close the remaining gap.

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 all seven parameters already carry their own semantics including the 1-50 limit and the two different defaults. The description only restates the strike+expiration+option_type dependency, adding little beyond what the schema documents.

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 names a specific resource (option chain for a single underlying ticker) and explicitly splits into two behaviors: expiration/liquid contract listing versus historical contract bars plus Black-Scholes Greeks when strike/expiration/option_type are supplied. No sibling tool (get_quote, get_price_history, analyze_ticker) touches options, and the description makes that scope unmistakable.

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 gives an explicit trigger for the second mode: 'When strike is also provided (with expiration and option_type call/put), returns historical daily OHLCV...'. What's missing is any explicit statement of when to prefer get_quote or get_price_history for plain underlying prices, or when the historical mode is the right choice versus the chain mode for expired contracts.

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

All ApexTick Market Data & Options MCP 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