Skip to main content
Glama
maven81g

TradeStation MCP Server

by maven81g

getOrderDetails

Retrieve comprehensive order information including status, execution details, and account data from TradeStation's trading platform for order tracking and management.

Instructions

Get detailed information for a specific order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdNoAccount ID (optional, uses TRADESTATION_ACCOUNT_ID from env if not provided)
orderIdYesOrder ID

Implementation Reference

  • Handler function that retrieves detailed information for a specific order by making an authenticated API request to `/brokerage/accounts/{accountId}/orders/{orderId}` and returns the JSON response.
    async (args) => {
      try {
        const accountId = args.accountId || TS_ACCOUNT_ID;
        const { orderId } = args;
    
        if (!accountId) {
          throw new Error('Account ID is required. Either provide accountId parameter or set TRADESTATION_ACCOUNT_ID in .env file.');
        }
    
        const orderDetails = await makeAuthenticatedRequest(
          `/brokerage/accounts/${encodeURIComponent(accountId)}/orders/${encodeURIComponent(orderId)}`
        );
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(orderDetails, null, 2)
            }
          ]
        };
      } catch (error: unknown) {
        return {
          content: [
            {
              type: "text",
              text: `Failed to fetch order details: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Zod schema defining input parameters for the getOrderDetails tool: optional accountId and required orderId.
    const orderDetailsSchema = {
      accountId: z.string().optional().describe('Account ID (optional, uses TRADESTATION_ACCOUNT_ID from env if not provided)'),
      orderId: z.string().describe('Order ID')
    };
  • src/index.ts:590-627 (registration)
    MCP server registration of the getOrderDetails tool, specifying name, description, input schema, and handler function.
    server.tool(
      "getOrderDetails",
      "Get detailed information for a specific order",
      orderDetailsSchema,
      async (args) => {
        try {
          const accountId = args.accountId || TS_ACCOUNT_ID;
          const { orderId } = args;
    
          if (!accountId) {
            throw new Error('Account ID is required. Either provide accountId parameter or set TRADESTATION_ACCOUNT_ID in .env file.');
          }
    
          const orderDetails = await makeAuthenticatedRequest(
            `/brokerage/accounts/${encodeURIComponent(accountId)}/orders/${encodeURIComponent(orderId)}`
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(orderDetails, null, 2)
              }
            ]
          };
        } catch (error: unknown) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to fetch order details: ${error instanceof Error ? error.message : 'Unknown error'}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • Shared utility function that handles token refresh, authentication headers, and API calls to TradeStation, used by the getOrderDetails handler.
    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');
        }
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't clarify authentication requirements, rate limits, error conditions, or what 'detailed information' includes (e.g., order status, timestamps, or financial details). This leaves significant gaps for an agent to understand the tool's behavior.

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, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently communicates the essential action without unnecessary elaboration.

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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'detailed information' includes, how results are structured, or potential limitations. Given the context of financial trading (inferred from sibling tools), more detail on return values like order status, quantities, or prices would be helpful for an agent.

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 description doesn't add any parameter-specific information beyond what's already in the schema (which has 100% coverage). It doesn't explain the relationship between 'accountId' and 'orderId', or provide examples of valid order IDs. Since the schema fully documents both parameters, 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.

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 ('detailed information for a specific order'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'getOrders' (which likely lists multiple orders) or 'getExecutions' (which might show order executions), leaving room for potential confusion.

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 'getOrders' for listing orders or 'getExecutions' for order execution details, nor does it specify prerequisites or contextual constraints beyond needing an order ID.

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