Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

queryOpenOrder

Check the status and details of active cryptocurrency futures orders on Aster exchange using symbol, order ID, or client order ID parameters.

Instructions

Query current open order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdNo
origClientOrderIdNo
symbolYes

Implementation Reference

  • src/index.ts:358-370 (registration)
    Registration of the 'queryOpenOrder' tool in the ListTools response, including its input schema definition.
    {
      name: 'queryOpenOrder',
      description: 'Query current open order.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          orderId: { type: 'number' },
          origClientOrderId: { type: 'string' },
        },
        required: ['symbol'],
      },
    },
  • Input schema for the queryOpenOrder tool.
    {
      name: 'queryOpenOrder',
      description: 'Query current open order.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          orderId: { type: 'number' },
          origClientOrderId: { type: 'string' },
        },
        required: ['symbol'],
      },
    },
  • Handler for queryOpenOrder tool: makes a signed GET request to the /fapi/v1/openOrder Aster API endpoint.
    case 'queryOpenOrder':
        return makeRequest('GET', '/fapi/v1/openOrder', args, true);
  • Shared helper function makeRequest used by all signed tools, including queryOpenOrder, to make authenticated API calls to Asterdex.
    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;
      }
    };
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 'query', implying a read operation, but doesn't specify if it requires authentication, has rate limits, returns real-time data, or handles errors. The description is too vague to inform the agent about key behavioral traits 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence with no wasted words, making it easy to parse. However, it's overly brief to the point of under-specification, which slightly reduces its effectiveness, but it remains well-structured and front-loaded.

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 (3 parameters, 0% schema coverage, no output schema, and no annotations), the description is incomplete. It doesn't explain parameter usage, return values, or behavioral aspects, leaving significant gaps for the agent to operate correctly in a context with many sibling tools.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions no parameters, failing to explain the meaning of 'orderId', 'origClientOrderId', or 'symbol' (which is required). This leaves the agent guessing about how to use these inputs effectively, with no added value beyond the schema.

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

Purpose2/5

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

The description 'Query current open order' restates the tool name 'queryOpenOrder' with minimal elaboration, making it tautological. It specifies the action ('query') and resource ('open order') but lacks specificity about what 'query' entails (e.g., retrieve details, check status) and doesn't distinguish it from sibling tools like 'getAllOpenOrders' or 'queryOrder', leaving ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this is for a single order versus multiple orders (compared to 'getAllOpenOrders'), or how it differs from 'queryOrder' (which might handle closed orders). The description offers no context on prerequisites, exclusions, or typical use cases.

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