Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

getTradeList

Retrieve cryptocurrency trade history for a specific trading pair and account on Aster Finance, allowing users to analyze transaction data within specified timeframes and parameters.

Instructions

Get trades for a specific account and symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeNo
fromIdNo
limitNo
startTimeNo
symbolYes

Implementation Reference

  • The handler logic for 'getTradeList' tool, which makes a signed GET request to the Aster API endpoint '/fapi/v1/userTrades'.
    case 'getTradeList':
        return makeRequest('GET', '/fapi/v1/userTrades', args, true);
  • src/index.ts:461-475 (registration)
    Registration of the 'getTradeList' tool in the ListTools response, including name, description, and input schema definition.
    {
      name: 'getTradeList',
      description: 'Get trades for a specific account and symbol.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          startTime: { type: 'number' },
          endTime: { type: 'number' },
          fromId: { type: 'number' },
          limit: { type: 'number' },
        },
        required: ['symbol'],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get trades' which implies a read operation, but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or what 'trades' includes (e.g., time range, status). This is inadequate for a tool with 5 parameters and no output schema.

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, straightforward sentence that is front-loaded with the core action. However, it could be more concise by avoiding the vague 'specific account' since 'account' isn't a parameter, and it lacks necessary details for clarity.

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, no output schema, and multiple sibling tools, the description is incomplete. It fails to explain parameter usage, return values, or how this tool differs from others, 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. It mentions 'account and symbol', but only 'symbol' is a documented parameter; 'account' is not in the schema. It doesn't explain the meaning of parameters like 'endTime', 'startTime', 'limit', or 'fromId', leaving them undocumented.

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

Purpose3/5

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

The description states the verb 'Get' and resource 'trades', but lacks specificity about what 'trades' means in this context (e.g., historical trades, open trades, executed trades). It doesn't distinguish from siblings like 'trades', 'historicalTrades', or 'aggTrades', leaving ambiguity about scope.

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 'trades', 'historicalTrades', or 'aggTrades'. The description implies usage for a specific account and symbol, but doesn't clarify prerequisites, exclusions, or comparison to sibling tools.

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