Skip to main content
Glama
maven81g

TradeStation MCP Server

by maven81g

getSymbolDetails

Retrieve detailed information for trading symbols to access market data and make informed decisions using TradeStation's API.

Instructions

Get detailed symbol information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolsYesSingle symbol or comma-separated list of symbols

Implementation Reference

  • Full handler implementation and registration for the getSymbolDetails tool. Calls TradeStation API endpoint /marketdata/symbols/{symbols} to retrieve detailed symbol information.
    server.tool(
      "getSymbolDetails",
      "Get detailed symbol information",
      symbolDetailsSchema,
      async (args) => {
        try {
          const { symbols } = args;
    
          const symbolDetails = await makeAuthenticatedRequest(
            `/marketdata/symbols/${encodeURIComponent(symbols)}`
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(symbolDetails, null, 2)
              }
            ]
          };
        } catch (error: unknown) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to fetch symbol details: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • Zod input schema for getSymbolDetails tool, defining the required 'symbols' parameter as a string.
    const symbolDetailsSchema = {
      symbols: z.string().describe('Single symbol or comma-separated list of symbols')
    };
  • Shared helper function used by getSymbolDetails (and other tools) to make authenticated requests to TradeStation API, including automatic token refresh.
    async function makeAuthenticatedRequest(
      endpoint: string,
      method: AxiosRequestConfig['method'] = 'GET',
      data: any = null
    ): Promise<any> {
      const userTokens = tokenStore.get(DEFAULT_USER);
    
      if (!userTokens) {
        throw new Error('User not authenticated. Please set TRADESTATION_REFRESH_TOKEN in .env file.');
      }
    
      // Check if token is expired or about to expire (within 60 seconds)
      if (userTokens.expiresAt < Date.now() + 60000) {
        // Refresh the token
        const newTokens = await refreshToken(userTokens.refreshToken);
        tokenStore.set(DEFAULT_USER, newTokens);
      }
    
      try {
        const options: AxiosRequestConfig = {
          method,
          url: `${TS_API_BASE}${endpoint}`,
          headers: {
            'Authorization': `Bearer ${tokenStore.get(DEFAULT_USER)?.accessToken}`,
            'Content-Type': 'application/json',
            'Accept': 'application/json'
          },
          timeout: 60000
        };
    
        if (data && (method === 'POST' || method === 'PUT' || method === 'PATCH')) {
          options.data = data;
        }
    
        const response = await axios(options);
        return response.data;
      } catch (error: unknown) {
        if (error instanceof AxiosError) {
          const errorMessage = error.response?.data?.Message || error.response?.data?.message || error.message;
          const statusCode = error.response?.status;
          console.error(`API request error [${statusCode}]: ${errorMessage}`);
          console.error('Endpoint:', endpoint);
          throw new Error(`API Error (${statusCode}): ${errorMessage}`);
        } else if (error instanceof Error) {
          console.error('API request error:', error.message);
          throw error;
        } else {
          console.error('Unknown API request error:', error);
          throw new Error('Unknown API request error');
        }
      }
    }
  • src/index.ts:668-700 (registration)
    MCP server tool registration for getSymbolDetails using server.tool() method.
    server.tool(
      "getSymbolDetails",
      "Get detailed symbol information",
      symbolDetailsSchema,
      async (args) => {
        try {
          const { symbols } = args;
    
          const symbolDetails = await makeAuthenticatedRequest(
            `/marketdata/symbols/${encodeURIComponent(symbols)}`
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(symbolDetails, null, 2)
              }
            ]
          };
        } catch (error: unknown) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to fetch symbol details: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
Behavior2/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 of behavioral disclosure. It states 'Get detailed symbol information' but doesn't clarify if this is a read-only operation, requires authentication, has rate limits, or what the output format might be. For a tool with no annotations, this leaves significant gaps in understanding its behavior and constraints.

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: 'Get detailed symbol information'. It's front-loaded with the core action and resource, with zero wasted words. Every part of the sentence contributes directly to the tool's purpose, making it highly concise and well-structured.

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 complex data (implied by 'detailed'). It doesn't address what 'detailed' includes, error handling, or response structure. With no structured fields to compensate, the description should provide more context to be fully helpful.

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 input schema has 100% description coverage, with the 'symbols' parameter clearly documented as a 'Single symbol or comma-separated list of symbols'. The description adds no additional meaning beyond this, as it doesn't elaborate on symbol formats, examples, or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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

Purpose3/5

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

The description 'Get detailed symbol information' states a clear verb ('Get') and resource ('symbol information'), but it's vague about what constitutes 'detailed' information. It doesn't distinguish this tool from sibling tools like 'searchSymbols' or 'marketData', which might also provide symbol-related data. The purpose is understandable but lacks specificity.

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. With siblings like 'searchSymbols' and 'marketData' available, there's no indication of whether this tool is for lookup, search, or real-time data, nor any prerequisites or exclusions mentioned. Usage is implied but not explicitly defined.

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