Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

historicalTrades

Retrieve past cryptocurrency market trades from Aster Finance to analyze trading patterns and market activity for informed decision-making.

Instructions

Get older market historical trades.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromIdNoTradeId to fetch from.
limitNoNumber of results. Default 500, max 1000.
symbolYesTrading symbol

Implementation Reference

  • Handler for the historicalTrades tool. Dispatches a GET request to the Aster API endpoint '/fapi/v1/historicalTrades' with provided arguments using the shared makeRequest utility.
    case 'historicalTrades':
      return makeRequest('GET', '/fapi/v1/historicalTrades', args);
  • Input schema definition for the historicalTrades tool, specifying parameters like symbol (required), limit, and fromId.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string', description: 'Trading symbol' },
        limit: { type: 'number', description: 'Number of results. Default 500, max 1000.' },
        fromId: { type: 'number', description: 'TradeId to fetch from.' },
      },
      required: ['symbol'],
    },
  • src/index.ts:79-91 (registration)
    Tool registration entry for historicalTrades in the listTools response, including name, description, and input schema.
    {
      name: 'historicalTrades',
      description: 'Get older market historical trades.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string', description: 'Trading symbol' },
          limit: { type: 'number', description: 'Number of results. Default 500, max 1000.' },
          fromId: { type: 'number', description: 'TradeId to fetch from.' },
        },
        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 the full burden of behavioral disclosure. It mentions 'older' trades, implying a focus on past data, but fails to detail critical aspects like rate limits, authentication requirements, pagination behavior, or error handling. This is inadequate for a tool that likely interacts with market data.

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 with no wasted words. It's front-loaded and directly states the tool's function, making it easy to parse quickly without 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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'older' entails, how results are returned, or any prerequisites for use. For a tool with three parameters and no structured behavioral hints, more context is needed to ensure proper agent invocation.

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%, with clear documentation for 'fromId', 'limit', and 'symbol' parameters. The description adds no additional meaning beyond the schema, such as explaining what 'older' means in relation to 'fromId' or default behaviors. This meets the baseline score since the schema handles the heavy lifting.

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 'Get older market historical trades' clearly states the verb ('Get') and resource ('older market historical trades'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'trades' or 'getTradeList', which likely also retrieve trade data, leaving some ambiguity about its specific 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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools such as 'trades' and 'getTradeList' present, there's no indication of what makes 'historicalTrades' unique—whether it's for archived data, different timeframes, or other criteria—leaving the agent to guess based on the name alone.

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