Skip to main content
Glama
maven81g

TradeStation MCP Server

by maven81g

getOptionStrikes

Retrieve available strike prices for options contracts on a specified underlying symbol, with optional expiration date filtering to identify trading opportunities.

Instructions

Get available strike prices for options on an underlying symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
underlyingYesUnderlying symbol (e.g., AAPL, SPY)
expirationNoExpiration date filter in YYYY-MM-DD format (optional)

Implementation Reference

  • The handler function for the getOptionStrikes tool. It constructs the API endpoint based on underlying symbol and optional expiration, calls makeAuthenticatedRequest to fetch strikes from TradeStation API, and returns JSON-formatted response or error.
    server.tool(
      "getOptionStrikes",
      "Get available strike prices for options on an underlying symbol",
      optionStrikesSchema,
      async (args) => {
        try {
          const { underlying, expiration } = args;
    
          let endpoint = `/marketdata/options/strikes/${encodeURIComponent(underlying)}`;
    
          if (expiration) {
            endpoint += `?expiration=${encodeURIComponent(expiration)}`;
          }
    
          const strikes = await makeAuthenticatedRequest(endpoint);
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(strikes, null, 2)
              }
            ]
          };
        } catch (error: unknown) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to fetch option strikes: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • Zod input schema defining parameters for the getOptionStrikes tool: required 'underlying' symbol and optional 'expiration' date.
    const optionStrikesSchema = {
      underlying: z.string().describe('Underlying symbol (e.g., AAPL, SPY)'),
      expiration: z.string().optional().describe('Expiration date filter in YYYY-MM-DD format (optional)')
    };
  • src/index.ts:401-437 (registration)
    MCP server.tool registration for getOptionStrikes, specifying name, description, input schema, and handler function.
    server.tool(
      "getOptionStrikes",
      "Get available strike prices for options on an underlying symbol",
      optionStrikesSchema,
      async (args) => {
        try {
          const { underlying, expiration } = args;
    
          let endpoint = `/marketdata/options/strikes/${encodeURIComponent(underlying)}`;
    
          if (expiration) {
            endpoint += `?expiration=${encodeURIComponent(expiration)}`;
          }
    
          const strikes = await makeAuthenticatedRequest(endpoint);
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(strikes, null, 2)
              }
            ]
          };
        } catch (error: unknown) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to fetch option strikes: ${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 the full burden of behavioral disclosure. It states what the tool does but lacks details on permissions, rate limits, response format, or error handling. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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. It doesn't explain what the return values look like (e.g., list of strikes, format), error conditions, or behavioral traits, which are crucial for a tool with no structured data to compensate.

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%, so the schema already documents both parameters ('underlying' and 'expiration') with clear descriptions. The description implies these parameters but adds no additional meaning beyond what the schema provides, meeting the baseline for high coverage.

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 verb ('Get') and resource ('available strike prices for options on an underlying symbol'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'getOptionExpirations' or 'getSymbolDetails', which could provide related information, so it doesn't reach the highest score.

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. It doesn't mention sibling tools like 'getOptionExpirations' for expiration dates or 'searchSymbols' for symbol lookup, nor does it specify prerequisites or exclusions, leaving usage context unclear.

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