Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

getAllOpenOrders

Retrieve all active trading orders for a specific cryptocurrency symbol to monitor positions and manage order execution.

Instructions

Get all open orders on a symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNo

Implementation Reference

  • Handler case for getAllOpenOrders tool that dispatches a signed GET request to Binance Futures API /fapi/v1/openOrders endpoint with provided arguments.
    case 'getAllOpenOrders':
        return makeRequest('GET', '/fapi/v1/openOrders', args, true);
  • Input schema definition for getAllOpenOrders tool, specifying an object with optional 'symbol' property.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string' },
      },
    },
  • src/index.ts:371-380 (registration)
    Registration of the getAllOpenOrders tool in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'getAllOpenOrders',
      description: 'Get all open orders on a symbol.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
        },
      },
    },
  • Generic helper function makeRequest used by all tool handlers, including getAllOpenOrders, to make authenticated HTTP requests to the Binance API.
    const makeRequest = async (method: 'GET' | 'POST' | 'DELETE', path: string, params: any, isSigned = false) => {
      try {
        let config: any = {
          method,
          url: path,
        };
    
        if (isSigned) {
          if (!API_KEY || !API_SECRET) {
            throw new McpError(ErrorCode.InvalidRequest, 'API_KEY and API_SECRET must be configured.');
          }
          params.timestamp = Date.now();
          const queryString = new URLSearchParams(params).toString();
          const signature = crypto.createHmac('sha256', API_SECRET).update(queryString).digest('hex');
          params.signature = signature;
          
          config.headers = { 'X-MBX-APIKEY': API_KEY };
        }
        
        if (method === 'GET' || method === 'DELETE') {
          config.params = params;
        } else { // POST
          config.data = new URLSearchParams(params).toString();
          config.headers = { ...config.headers, 'Content-Type': 'application/x-www-form-urlencoded' };
        }
    
        const response = await this.axiosInstance.request(config);
        return { content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }] };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new McpError(
            ErrorCode.InternalError,
            `Aster API error: ${error.response?.data?.msg || error.message}`
          );
        }
        throw error;
      }
    };
Behavior1/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 fails to describe key traits: whether this is a read-only operation, if it requires authentication, potential rate limits, pagination behavior, or the format of returned data. The description is minimal and offers no behavioral context beyond the basic action.

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 is appropriately sized and front-loaded, directly stating the tool's 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 complexity of a financial API tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on authentication, return format, error handling, and usage context, making it inadequate for an AI agent to reliably invoke this tool in a trading environment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, and the description only mentions 'on a symbol' without explaining what 'symbol' represents (e.g., trading pair format like BTCUSDT), its required status, or any constraints. It adds minimal meaning beyond the schema, insufficiently compensating for the low 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 'all open orders on a symbol', making the purpose specific and understandable. It distinguishes from siblings like 'getAllOrders' (which likely includes closed orders) and 'queryOpenOrder' (which might query a single order), though it doesn't explicitly name these alternatives.

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 like 'getAllOrders' or 'queryOpenOrder'. It lacks context about prerequisites, such as authentication needs or account permissions, and doesn't mention any exclusions or constraints beyond the symbol parameter.

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/questflowai/aster-mcp-server'

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