Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

getAllOrders

Retrieve all cryptocurrency trading orders from your Aster Finance account, including active, canceled, and filled orders, filtered by symbol and time range.

Instructions

Get all account orders; active, canceled, or filled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeNo
limitNo
orderIdNo
startTimeNo
symbolYes

Implementation Reference

  • The handler for the 'getAllOrders' tool. It calls the shared makeRequest function to perform a signed GET request to the Aster Futures API endpoint '/fapi/v1/allOrders'.
    case 'getAllOrders':
        return makeRequest('GET', '/fapi/v1/allOrders', args, true);
  • Input schema definition for the getAllOrders tool, specifying parameters like symbol (required), orderId, timestamps, and limit.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string' },
        orderId: { type: 'number' },
        startTime: { type: 'number' },
        endTime: { type: 'number' },
        limit: { type: 'number' },
      },
      required: ['symbol'],
    },
  • src/index.ts:381-395 (registration)
    Registration of the getAllOrders tool in the MCP server's listTools response, including name, description, and input schema.
    {
      name: 'getAllOrders',
      description: 'Get all account orders; active, canceled, or filled.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          orderId: { type: 'number' },
          startTime: { type: 'number' },
          endTime: { type: 'number' },
          limit: { type: 'number' },
        },
        required: ['symbol'],
      },
    },
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 provides minimal behavioral information. It states it's a read operation ('Get'), but doesn't disclose pagination behavior, rate limits, authentication requirements, response format, or whether it returns real-time or historical data. For a tool with 5 parameters and no annotation coverage, this is inadequate disclosure.

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?

Extremely concise single sentence with no wasted words. The description is front-loaded with the core purpose and includes important scope information. Every word earns its place, though the brevity comes at the cost of completeness.

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 tool with 5 parameters, 0% schema coverage, no annotations, and no output schema, the description is severely incomplete. It provides basic purpose but lacks parameter documentation, behavioral context, usage guidance, and output information. The conciseness is achieved through under-specification rather than efficient communication.

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 provides no parameter information. The 5 parameters (endTime, limit, orderId, startTime, symbol) are completely undocumented in both schema and description. The description mentions 'all account orders' which implies the 'symbol' parameter might filter by trading pair, but this is only implied, not stated.

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 account orders'), and specifies the scope ('active, canceled, or filled'). It distinguishes from sibling 'getAllOpenOrders' by including all statuses, but doesn't explicitly mention this distinction. The purpose is clear but could be more specific about what makes it different from similar tools.

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 on when to use this tool versus alternatives like 'getAllOpenOrders', 'queryOrder', or 'getTradeList'. The description implies it retrieves all orders regardless of status, but doesn't provide context about when this broad retrieval is appropriate versus more targeted queries. No mention of prerequisites, limitations, or performance considerations.

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