Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

getForceOrders

Retrieve cryptocurrency force orders including liquidations and ADL events from Aster Finance Futures API to monitor automated position closures and analyze market conditions.

Instructions

Get user's force orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
autoCloseTypeNo
endTimeNo
limitNo
startTimeNo
symbolNo

Implementation Reference

  • Handler for the getForceOrders tool: makes a signed GET request to the /fapi/v1/forceOrders Aster API endpoint with the provided arguments.
    case 'getForceOrders':
        return makeRequest('GET', '/fapi/v1/forceOrders', args, true);
  • Schema definition for the getForceOrders tool, specifying input parameters: symbol (string), autoCloseType (enum: LIQUIDATION/ADL), startTime/endTime (number), limit (number).
    {
      name: 'getForceOrders',
      description: "Get user's force orders.",
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          autoCloseType: { type: 'string', enum: ['LIQUIDATION', 'ADL'] },
          startTime: { type: 'number' },
          endTime: { type: 'number' },
          limit: { type: 'number' },
        },
      },
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is read-only, requires authentication, has rate limits, or what the output entails, which is inadequate for a tool with parameters.

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 extremely concise with one short sentence, which is front-loaded and wastes no words. However, it's overly terse to the point of under-specification.

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 5 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It fails to explain the tool's purpose in context, parameter usage, or expected behavior, making it insufficient for effective agent use.

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 'force orders' are, how parameters like 'autoCloseType' or time ranges apply, leaving semantics unclear.

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 'Get user's force orders' restates the tool name with minimal elaboration, making it tautological. It specifies the resource ('force orders') but lacks a clear verb beyond 'get' and doesn't differentiate from sibling tools like 'getAllOrders' or 'queryOrder'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. It doesn't mention prerequisites, context, or exclusions, leaving the agent with no usage direction.

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