Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

aggTrades

Retrieve compressed aggregate market trades for cryptocurrency symbols to analyze trading patterns and market activity with timestamp and volume data.

Instructions

Get compressed, aggregate market trades.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeNoTimestamp in ms to get aggregate trades until INCLUSIVE.
fromIdNoID to get aggregate trades from INCLUSIVE.
limitNoNumber of results. Default 500, max 1000.
startTimeNoTimestamp in ms to get aggregate trades from INCLUSIVE.
symbolYesTrading symbol

Implementation Reference

  • Handler logic for the 'aggTrades' tool. Matches the tool name in the switch statement and calls makeRequest to GET /fapi/v1/aggTrades with input arguments.
    case 'aggTrades':
      return makeRequest('GET', '/fapi/v1/aggTrades', args);
  • Input schema for the aggTrades tool, defining the expected parameters and their types/descriptions.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string', description: 'Trading symbol' },
        fromId: { type: 'number', description: 'ID to get aggregate trades from INCLUSIVE.' },
        startTime: { type: 'number', description: 'Timestamp in ms to get aggregate trades from INCLUSIVE.' },
        endTime: { type: 'number', description: 'Timestamp in ms to get aggregate trades until INCLUSIVE.' },
        limit: { type: 'number', description: 'Number of results. Default 500, max 1000.' },
      },
      required: ['symbol'],
  • src/index.ts:92-105 (registration)
    Registration of the aggTrades tool in the ListToolsRequestSchema response array, including name, description, and schema.
    {
      name: 'aggTrades',
      description: 'Get compressed, aggregate market trades.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string', description: 'Trading symbol' },
          fromId: { type: 'number', description: 'ID to get aggregate trades from INCLUSIVE.' },
          startTime: { type: 'number', description: 'Timestamp in ms to get aggregate trades from INCLUSIVE.' },
          endTime: { type: 'number', description: 'Timestamp in ms to get aggregate trades until INCLUSIVE.' },
          limit: { type: 'number', description: 'Number of results. Default 500, max 1000.' },
        },
        required: ['symbol'],
      },
  • Shared utility function makeRequest used by all tool handlers, including aggTrades, to perform HTTP requests to the AsterDex Futures API, with optional signing for private endpoints.
    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 the full burden of behavioral disclosure. It mentions 'compressed, aggregate' trades but doesn't explain what this means operationally (e.g., data format, aggregation method, rate limits, or authentication needs). This leaves significant gaps in understanding the tool's behavior and constraints.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. It's appropriately sized for a tool with well-documented parameters in the schema, making it easy to parse quickly.

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 complexity of a financial data tool with 5 parameters and no output schema or annotations, the description is insufficient. It doesn't explain the output format, aggregation details, or error handling, leaving the agent with incomplete context for effective use.

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 100%, so the input schema fully documents all parameters. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters (e.g., 'fromId' vs. time-based filters) or typical use cases. Baseline 3 is appropriate when the schema handles parameter documentation.

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 ('Get') and resource ('compressed, aggregate market trades'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'trades' or 'historicalTrades', which likely provide similar trade data in different formats or scopes.

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 is provided on when to use this tool versus alternatives such as 'trades' or 'historicalTrades'. The description lacks context about use cases, prerequisites, or comparisons with sibling tools, leaving the agent without direction on tool selection.

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