Skip to main content
Glama
maven81g

TradeStation MCP Server

by maven81g

searchSymbols

Find trading symbols by name or criteria across stocks, options, futures, and forex to identify assets for market analysis and order placement.

Instructions

Search for symbols (Note: Symbol search not available in TradeStation v3 API - use getSymbolDetails instead with known symbols)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
criteriaYesSearch criteria
typeNoSymbol type filterall

Implementation Reference

  • The handler function for the 'searchSymbols' tool, registered via server.tool(). This is a placeholder implementation that returns an error message explaining that symbol search is not supported by the TradeStation v3 API and suggests alternatives.
    server.tool(
      "searchSymbols",
      "Search for symbols (Note: Symbol search not available in TradeStation v3 API - use getSymbolDetails instead with known symbols)",
      searchSymbolsSchema,
      async (args) => {
        try {
          const { criteria } = args;
    
          return {
            content: [
              {
                type: "text",
                text: `Symbol search is not available in TradeStation API v3.\n\nAlternatives:\n1. Use getSymbolDetails with known symbols: "${criteria}"\n2. Use marketData to get quotes for known symbols\n3. For options, use getOptionExpirations and getOptionStrikes with the underlying symbol`
              }
            ],
            isError: true
          };
        } catch (error: unknown) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to search symbols: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • Zod schema defining the input parameters for the searchSymbols tool: criteria (string) and type (enum with default 'all').
    const searchSymbolsSchema = {
      criteria: z.string().describe('Search criteria'),
      type: z.enum(['stock', 'option', 'future', 'forex', 'all'])
        .default('all')
        .describe('Symbol type filter')
    };
  • src/index.ts:336-365 (registration)
    Registration of the 'searchSymbols' tool using McpServer's tool() method, including name, description, schema, and inline handler.
    server.tool(
      "searchSymbols",
      "Search for symbols (Note: Symbol search not available in TradeStation v3 API - use getSymbolDetails instead with known symbols)",
      searchSymbolsSchema,
      async (args) => {
        try {
          const { criteria } = args;
    
          return {
            content: [
              {
                type: "text",
                text: `Symbol search is not available in TradeStation API v3.\n\nAlternatives:\n1. Use getSymbolDetails with known symbols: "${criteria}"\n2. Use marketData to get quotes for known symbols\n3. For options, use getOptionExpirations and getOptionStrikes with the underlying symbol`
              }
            ],
            isError: true
          };
        } catch (error: unknown) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to search symbols: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses a critical behavioral trait: that symbol search is not available in TradeStation v3 API, which is essential context beyond what the input schema provides. However, it doesn't mention other potential behaviors like rate limits, authentication needs, or what happens when the search fails, leaving some 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 extremely concise and front-loaded, consisting of just two sentences that directly address the tool's purpose and critical usage limitation. Every sentence earns its place by providing essential information without any wasted words.

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?

Given the tool's complexity (search functionality with API limitations), no annotations, and no output schema, the description is mostly complete. It covers the purpose, usage guidelines, and a key behavioral limitation. However, it lacks details on what the search returns (e.g., format, pagination) or error handling, which would be helpful for full completeness.

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 the schema already documents both parameters ('criteria' and 'type') with descriptions and enum values. The description does not add any additional meaning or context about the parameters beyond what the schema provides, so it meets the baseline of 3.

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 clearly states the tool's purpose with a specific verb ('Search for symbols') and resource ('symbols'), and explicitly distinguishes it from the sibling tool 'getSymbolDetails' by noting that symbol search is not available in TradeStation v3 API and to use getSymbolDetails instead with known symbols. This provides clear differentiation from alternatives.

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?

The description provides explicit guidance on when to use this tool vs. alternatives by stating 'Symbol search not available in TradeStation v3 API - use getSymbolDetails instead with known symbols.' This clearly indicates when not to use this tool and names the alternative, offering complete usage context.

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