Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

getIncomeHistory

Retrieve cryptocurrency trading income history from Aster Finance to analyze past earnings, track performance, and review transaction records for informed financial decisions.

Instructions

Get income history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeNo
incomeTypeNo
limitNo
startTimeNo
symbolNo

Implementation Reference

  • Handler implementation for the getIncomeHistory tool. It makes a signed GET request to the Aster Futures API endpoint '/fapi/v1/income' with the input arguments to retrieve income history.
    case 'getIncomeHistory':
        return makeRequest('GET', '/fapi/v1/income', args, true);
  • Input schema definition and tool registration for getIncomeHistory in the ListTools response. Specifies parameters like symbol, incomeType, time range, and limit.
    {
      name: 'getIncomeHistory',
      description: 'Get income history.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          incomeType: { type: 'string' },
          startTime: { type: 'number' },
          endTime: { type: 'number' },
          limit: { type: 'number' },
        },
      },
    },
  • src/index.ts:476-489 (registration)
    The getIncomeHistory tool is registered here in the array of tools returned by ListToolsRequestSchema.
    {
      name: 'getIncomeHistory',
      description: 'Get income history.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          incomeType: { type: 'string' },
          startTime: { type: 'number' },
          endTime: { type: 'number' },
          limit: { type: 'number' },
        },
      },
    },
Behavior1/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. 'Get income history' only indicates a read operation but provides no information about authentication requirements, rate limits, pagination behavior, error conditions, data freshness, or what constitutes 'income' in this context. For a tool with 5 parameters and no output schema, this leaves critical behavioral aspects completely undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just three words, which could be appropriate if it were more informative. However, this brevity comes at the cost of under-specification rather than efficient communication. While it's front-loaded (the entire description is the purpose statement), it lacks the additional context needed for a tool with multiple parameters and no annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 parameters, no annotations, no output schema, and many sibling financial tools), the description is completely inadequate. It doesn't explain what 'income' means in this context, how parameters filter results, what the return format looks like, or how this tool differs from other financial data tools. The agent would struggle to use this tool correctly without significant trial and error or external documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage for all 5 parameters (endTime, incomeType, limit, startTime, symbol), the description provides absolutely no information about what these parameters mean, their expected formats, or how they affect the query. The description doesn't mention any parameters at all, failing completely to compensate for the schema's lack of documentation. This leaves the agent guessing about how to construct valid requests.

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 income history' is a tautology that essentially restates the tool name 'getIncomeHistory' without adding meaningful specificity. It doesn't clarify what type of income (trading fees, interest, etc.), whose income (account-level, position-level), or what format the history takes. While it includes a verb ('Get') and resource ('income history'), it lacks the specificity needed to distinguish it from potential sibling tools or understand its exact scope.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like getAccountInfo, getBalance, getTradeList, and getPositionMarginHistory that might overlap with financial data, there's no indication of whether this tool is for comprehensive income reporting, specific income types, or particular contexts. The agent receives no help in selecting this tool appropriately among the many financial data tools available.

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