Skip to main content
Glama

Option Expirations

GetOptionExpirations
Read-only

List the available option expiration dates for a stock, with the contract count at each. Use this to pick an expiration for GetOptionChain. Pass expired=true for past expirations (US tickers), to pick one for GetOptionChainSession. For a TSX/TSXV listing or an NSE share or index pass MIC:TICKER, e.g. XTSE:RY, XNSE:NIFTY.

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": "GetOptionExpirations"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker, e.g. AAPL, or MIC:TICKER for a TSX or TSXV listing or an NSE share or index, e.g. XTSE:RY, XNSE:NIFTY
endDateNoWith expired=true: last expiration date in YYYY-MM-DD format (default: yesterday)
expiredNoList past expirations instead of upcoming ones (default: false)
startDateNoWith expired=true: first expiration date in YYYY-MM-DD format (default: 90 days before endDate)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker, e.g. AAPL, or MIC:TICKER for a TSX or TSXV listing, e.g. XTSE:RY"New value: +"Stock ticker, e.g. AAPL, or MIC:TICKER for a TSX or TSXV listing or an NSE share or index, e.g. XTSE:RY, XNSE:NIFTY"
  2. Changed3 schema fields changed
    • addedInput schema / properties / endDate
      Added value: +{
      +  "default": null,
      +  "description": "With expired=true: last expiration date in YYYY-MM-DD format (default: yesterday)",
      +  "type": "string"
      +}
    • addedInput schema / properties / expired
      Added value: +{
      +  "default": false,
      +  "description": "List past expirations instead of upcoming ones (default: false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / startDate
      Added value: +{
      +  "default": null,
      +  "description": "With expired=true: first expiration date in YYYY-MM-DD format (default: 90 days before endDate)",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker, e.g. AAPL"New value: +"Stock ticker, e.g. AAPL, or MIC:TICKER for a TSX or TSXV listing, e.g. XTSE:RY"
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered and the description correctly avoids repeating it. It adds behavior beyond the annotations: that the response includes a per-date contract count, that expired=true applies only to US tickers, and the MIC:TICKER addressing convention for TSX/TSXV and NSE. It stops short of mentioning ordering of the returned dates or error behavior for bad tickers, so it is not fully complete.

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?

Four compact sentences, each doing distinct work: purpose, primary consumer, expired-branch consumer, and ticker addressing. The purpose is front-loaded and nothing is repeated from the structured fields verbatim beyond the necessary example.

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?

For a four-parameter read-only listing tool with no output schema, the description covers purpose, return content (dates plus contract counts), conditional parameter activation, and the sibling hand-off. Minor gaps remain around result ordering and failure modes, which are not addressed anywhere else in the definition.

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 contributes constraints the schema does not: expired=true is restricted to US tickers, and startDate/endDate are useful precisely because they pair with that flag when selecting a historical expiration for GetOptionChainSession. The MIC:TICKER example is duplicated from the schema, so the added value is real but partial.

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 opening sentence states a specific verb and resource ('List the available option expiration dates for a stock') and adds a scope detail ('with the contract count at each') that distinguishes it from the chain-retrieval siblings. An agent can tell this is the discovery step before GetOptionChain without opening any schema.

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?

It explicitly names the downstream consumers: 'Use this to pick an expiration for GetOptionChain', and routes the expired case to GetOptionChainSession. Both the when and the which-alternative conditions are stated outright rather than implied.

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.