Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

getPositionMarginHistory

Retrieve historical margin adjustments for cryptocurrency futures positions on Aster Finance, tracking changes over specified time periods to monitor position management activity.

Instructions

Get position margin change history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeNo
limitNo
startTimeNo
symbolYes
typeNo

Implementation Reference

  • src/index.ts:671-672 (handler)
    Handler for getPositionMarginHistory tool: makes a signed GET request to the Aster API endpoint '/fapi/v1/positionMargin/history'.
    case 'getPositionMarginHistory':
    return makeRequest('GET', '/fapi/v1/positionMargin/history', args, true);
  • src/index.ts:436-450 (registration)
    Registration of the getPositionMarginHistory tool in the listTools response, including description and input schema.
    {
  name: 'getPositionMarginHistory',
  description: 'Get position margin change history.',
  inputSchema: {
    type: 'object',
    properties: {
      symbol: { type: 'string' },
      type: { type: 'number', enum: [1, 2] },
      startTime: { type: 'number' },
      endTime: { type: 'number' },
      limit: { type: 'number' },
    },
    required: ['symbol'],
  },
},

Tool Definition Quality

C2.6/5.0
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 states it 'gets' data, implying a read-only operation, but doesn't clarify if it requires authentication, has rate limits, returns paginated results, or what the output format is. For a tool with 5 parameters and no output schema, this is a significant gap in transparency.

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 extremely concise—a single sentence with no wasted words. It's front-loaded with the core purpose, making it easy to scan. However, this conciseness comes at the cost of completeness, as noted in other dimensions.

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 (5 parameters, 0% schema coverage, no output schema, no annotations), the description is incomplete. It doesn't explain what the tool returns, how to interpret parameters like 'type', or behavioral aspects like error handling. For a financial data tool with multiple inputs, this lack of detail makes it inadequate for reliable 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 by explaining parameters. It mentions 'position margin change history', which hints at 'symbol' and possibly 'startTime'/'endTime', but doesn't define 'type' (with enum 1/2), 'limit', or the meaning of 'change history'. This leaves most parameters undocumented, failing to add sufficient meaning beyond the bare schema.

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 'Get position margin change history' clearly states the action (get) and resource (position margin change history), making the purpose understandable. However, it lacks specificity about what 'position margin' refers to (e.g., trading positions) and doesn't distinguish it from sibling tools like 'getPositionInfo' or 'modifyPositionMargin', leaving room for ambiguity.

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. It doesn't mention prerequisites, such as needing an active position, or differentiate it from related tools like 'getIncomeHistory' or 'getForceOrders', which might overlap in financial contexts. This absence of context makes it harder for an agent to select the correct tool.

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