Skip to main content
Glama
maven81g

TradeStation MCP Server

by maven81g

getOptionExpirations

Retrieve available expiration dates for options contracts on a specific underlying symbol to support trading decisions and strategy planning.

Instructions

Get available expiration dates for options on an underlying symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
underlyingYesUnderlying symbol (e.g., AAPL, SPY)

Implementation Reference

  • Input schema defining the 'underlying' parameter for the getOptionExpirations tool.
    const optionExpirationsSchema = {
      underlying: z.string().describe('Underlying symbol (e.g., AAPL, SPY)')
    };
  • The complete tool handler registration and implementation for 'getOptionExpirations'. It extracts the 'underlying' symbol from arguments, makes an authenticated API request to the TradeStation endpoint `/marketdata/options/expirations/{underlying}`, and returns the JSON response or error.
    server.tool(
      "getOptionExpirations",
      "Get available expiration dates for options on an underlying symbol",
      optionExpirationsSchema,
      async (args) => {
        try {
          const { underlying } = args;
    
          const expirations = await makeAuthenticatedRequest(
            `/marketdata/options/expirations/${encodeURIComponent(underlying)}`
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(expirations, null, 2)
              }
            ]
          };
        } catch (error: unknown) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to fetch option expirations: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose whether this is a read-only operation, potential rate limits, authentication needs, or what the return format looks like, leaving significant gaps.

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 a single, efficient sentence that directly states the tool's function with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool that likely returns structured data. It doesn't explain what 'available expiration dates' means in practice (e.g., date format, range, or filtering), leaving the agent with insufficient context for effective use.

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?

The schema description coverage is 100%, with the single parameter 'underlying' well-documented in the schema. The description adds no additional parameter semantics beyond implying it's for options, so it meets the baseline for high schema coverage without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get available expiration dates') and the resource ('options on an underlying symbol'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'getOptionStrikes' which likely retrieves different option data, missing explicit distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'getOptionStrikes' or 'getSymbolDetails', nor does it mention prerequisites or exclusions. It implies usage for options data but lacks contextual boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/maven81g/tradestation_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server