Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

countdownCancelAll

Cancel all open cryptocurrency trading orders after a specified countdown period to manage risk and automate order cleanup on the Aster exchange.

Instructions

Auto-cancel all open orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countdownTimeYesCountdown time in milliseconds.
symbolYes

Implementation Reference

  • Handler implementation for the countdownCancelAll tool. It makes a signed POST request to the /fapi/v1/countdownCancelAll endpoint on the Aster (Binance Futures) API with the provided arguments.
    case 'countdownCancelAll':
        return makeRequest('POST', '/fapi/v1/countdownCancelAll', args, true);
  • Input schema defining the parameters for the countdownCancelAll tool: symbol (string, required) and countdownTime (number in ms, required).
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string' },
        countdownTime: { type: 'number', description: 'Countdown time in milliseconds.' },
      },
      required: ['symbol', 'countdownTime'],
    },
  • src/index.ts:346-357 (registration)
    Registration of the countdownCancelAll tool in the MCP server's listTools response, including name, description, and input schema.
    {
      name: 'countdownCancelAll',
      description: 'Auto-cancel all open orders.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          countdownTime: { type: 'number', description: 'Countdown time in milliseconds.' },
        },
        required: ['symbol', 'countdownTime'],
      },
    },
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. While 'Auto-cancel' implies a destructive operation, it doesn't specify whether this requires authentication, has rate limits, what happens to partially filled orders, or if the cancellation is immediate versus scheduled. The description is too minimal 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 just three words, front-loading the core action. Every word earns its place with no wasted verbiage or 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 destructive tool with 2 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'Auto-cancel' means operationally, what the parameters control, or what happens after invocation. The context demands more completeness.

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 50% (only 'countdownTime' has a description). The description doesn't mention any parameters, so it adds no semantic value beyond what the schema provides. However, with 2 parameters total and one documented in schema, the baseline 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 action ('Auto-cancel') and target ('all open orders'), providing a specific verb+resource combination. However, it doesn't differentiate from the sibling tool 'cancelAllOpenOrders' which appears to serve a similar function, preventing a perfect score.

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 'cancelAllOpenOrders' or 'cancelBatchOrders'. It lacks context about prerequisites, timing considerations, or any explicit when/when-not instructions.

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