Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

cancelOrder

Cancel active cryptocurrency trading orders on the Aster exchange by specifying the trading symbol and order identifier to manage positions and execute trading strategies.

Instructions

Cancel an active order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdNo
origClientOrderIdNo
symbolYes

Implementation Reference

  • The handler for the 'cancelOrder' tool. It invokes the shared makeRequest function with a signed DELETE request to the '/fapi/v1/order' endpoint on the Aster API, passing the tool arguments.
    case 'cancelOrder':
        return makeRequest('DELETE', '/fapi/v1/order', args, true);
  • Input schema for the 'cancelOrder' tool, defining parameters: symbol (required), orderId, origClientOrderId.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string' },
        orderId: { type: 'number' },
        origClientOrderId: { type: 'string' },
      },
      required: ['symbol'],
    },
  • src/index.ts:309-321 (registration)
    Registration of the 'cancelOrder' tool in the ListTools response, specifying name, description, and input schema.
    {
      name: 'cancelOrder',
      description: 'Cancel an active order.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          orderId: { type: 'number' },
          origClientOrderId: { type: 'string' },
        },
        required: ['symbol'],
      },
    },
  • Shared helper function 'makeRequest' used by the cancelOrder handler (and others) to make authenticated HTTP requests to the Aster Futures API, including signing with API key/secret.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Cancel an active order' implies a destructive mutation, but it doesn't specify permissions required, whether cancellation is reversible, rate limits, error conditions (e.g., if order doesn't exist), or what happens on success (e.g., order status change). This leaves significant gaps for a mutation tool.

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 extremely concise with a single sentence that front-loads the core purpose. There is no wasted verbiage, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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's complexity (destructive mutation with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, parameter meanings, or return values, leaving the agent with insufficient context to use the tool effectively beyond basic inference.

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 but adds no parameter information. It doesn't explain what 'orderId', 'origClientOrderId', or 'symbol' represent, their formats, or that 'symbol' is required. For a tool with 3 parameters, this is inadequate, failing to clarify usage beyond the bare schema.

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 action ('Cancel') and target ('an active order'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'cancelAllOpenOrders' or 'cancelBatchOrders', which would require mentioning it cancels individual orders rather than batches or all open orders.

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 prerequisites (e.g., order must be active), exclusions (e.g., cannot cancel filled orders), or compare to siblings like 'cancelAllOpenOrders' for bulk operations or 'queryOrder' for checking status first.

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