Skip to main content
Glama

fetchOpenOrders

Retrieve all open orders from a cryptocurrency exchange account to monitor active trades and manage positions.

Instructions

Fetch all open orders using a configured account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNameYesAccount name defined in the configuration file (e.g., 'bybit_main')
symbolNoTrading symbol (e.g., 'BTC/USDT')
sinceNoTimestamp in ms to fetch orders since (optional)
limitNoLimit the number of orders returned (optional)
paramsNoAdditional exchange-specific parameters

Implementation Reference

  • The main handler function for the 'fetchOpenOrders' MCP tool. It retrieves the authenticated CCXT exchange instance, checks if the exchange supports fetchOpenOrders, executes the method with provided parameters (symbol, since, limit, params), and returns the result as JSON or an error response.
      async ({ accountName, symbol, since, limit, params }) => {
        try {
          const exchange = ccxtServer.getExchangeInstance(accountName);
    
          // getExchangeInstance가 성공하면 인증은 보장됨
    
          // fetchOpenOrders 메서드가 지원되는지 확인
          if (!exchange.has["fetchOpenOrders"]) {
            return {
              content: [
                {
                  type: "text",
                  text: `Account '${accountName}' (Exchange: ${exchange.id}) does not support fetching open orders`,
                },
              ],
              isError: true,
            };
          }
    
          const openOrders = await exchange.fetchOpenOrders(
            symbol,
            since,
            limit,
            params,
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(openOrders, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error fetching open orders for account '${accountName}': ${
                  (error as Error).message
                }`,
              },
            ],
            isError: true,
          };
        }
      },
    );
  • Zod input schema defining parameters for the fetchOpenOrders tool: accountName (string, required), symbol (string, optional), since (number, optional), limit (number, optional), params (record, optional).
    {
      accountName: z
        .string()
        .describe(
          "Account name defined in the configuration file (e.g., 'bybit_main')"
        ),
      symbol: z
        .string()
        .optional()
        .describe("Trading symbol (e.g., 'BTC/USDT')"),
      since: z
        .number()
        .optional()
        .describe("Timestamp in ms to fetch orders since (optional)"),
      limit: z
        .number()
        .optional()
        .describe("Limit the number of orders returned (optional)"),
      params: z
        .record(z.any())
        .optional()
        .describe("Additional exchange-specific parameters"),
    },
  • Local registration of the fetchOpenOrders tool within the registerOrderTools function using server.tool(name, description, inputSchema, handler).
    server.tool(
      "fetchOpenOrders",
      "Fetch all open orders using a configured account",
      {
        accountName: z
          .string()
          .describe(
            "Account name defined in the configuration file (e.g., 'bybit_main')"
          ),
        symbol: z
          .string()
          .optional()
          .describe("Trading symbol (e.g., 'BTC/USDT')"),
        since: z
          .number()
          .optional()
          .describe("Timestamp in ms to fetch orders since (optional)"),
        limit: z
          .number()
          .optional()
          .describe("Limit the number of orders returned (optional)"),
        params: z
          .record(z.any())
          .optional()
          .describe("Additional exchange-specific parameters"),
      },
      async ({ accountName, symbol, since, limit, params }) => {
        try {
          const exchange = ccxtServer.getExchangeInstance(accountName);
    
          // getExchangeInstance가 성공하면 인증은 보장됨
    
          // fetchOpenOrders 메서드가 지원되는지 확인
          if (!exchange.has["fetchOpenOrders"]) {
            return {
              content: [
                {
                  type: "text",
                  text: `Account '${accountName}' (Exchange: ${exchange.id}) does not support fetching open orders`,
                },
              ],
              isError: true,
            };
          }
    
          const openOrders = await exchange.fetchOpenOrders(
            symbol,
            since,
            limit,
            params,
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(openOrders, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error fetching open orders for account '${accountName}': ${
                  (error as Error).message
                }`,
              },
            ],
            isError: true,
          };
        }
      },
    );
  • src/server.ts:373-373 (registration)
    Top-level registration call to registerOrderTools in CcxtMcpServer.registerTools(), which includes registering the fetchOpenOrders tool.
    registerOrderTools(this.server, this);
  • Helper method used by the handler to retrieve the pre-loaded, authenticated CCXT Exchange instance for the specified accountName.
    getExchangeInstance(accountName: string): Exchange {
      const instance = this.exchangeInstances[accountName];
      if (!instance) {
        console.error(
          `No pre-loaded exchange instance found for account name: ${accountName}`,
        );
        // Consider listing available account names: Object.keys(this.exchangeInstances).join(', ')
        throw new Error(
          `Account configuration not found or failed to load for: ${accountName}`,
        );
      }
      return instance;
    }
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 the basic action. It doesn't disclose behavioral traits like whether this is a read-only operation, potential rate limits, authentication requirements, pagination behavior, or what happens if no orders exist. For a tool with 5 parameters and no annotation coverage, this is a significant gap.

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 with zero waste. It's appropriately sized for the tool's complexity and front-loads the core purpose 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?

Given the tool has 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'open orders' means in this context, what data is returned, or how results are structured. For a data-fetching tool in a trading environment, more context about return values and behavior is needed.

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 all parameters are documented in the schema. The description adds no additional parameter semantics beyond implying 'accountName' is required (which is already in the schema). The baseline of 3 is appropriate when the schema does the heavy lifting, though the description could have explained parameter interactions.

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 'fetch' and resource 'all open orders' with the context 'using a configured account', which makes the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'fetchOrder' or 'fetchClosedOrders', which would require more specific language about scope.

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 minimal guidance with 'using a configured account' but doesn't specify when to use this tool versus alternatives like 'fetchOrder' (for a single order) or 'fetchClosedOrders'. No explicit when-not-to-use scenarios or prerequisites are mentioned, leaving the agent to infer usage from context alone.

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/lazy-dinosaur/ccxt-mcp'

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