Aster Finance MCP Server

getPositionInfo

Retrieve current cryptocurrency position details including status, size, and value for specific trading symbols on the Aster Finance exchange.

Instructions

Get current position information.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getPositionInfo"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	No

Implementation Reference

src/index.ts:673-674 (handler)
The switch case that handles the 'getPositionInfo' tool invocation. It calls the shared makeRequest function with a signed GET to the '/fapi/v2/positionRisk' endpoint.
```
case 'getPositionInfo':
    return makeRequest('GET', '/fapi/v2/positionRisk', args, true);
```
src/index.ts:454-459 (schema)
Input schema definition for the 'getPositionInfo' tool, accepting an optional 'symbol' parameter.
```
inputSchema: {
  type: 'object',
  properties: {
    symbol: { type: 'string' },
  },
},
```

src/index.ts:451-460 (registration)

Registration of the 'getPositionInfo' tool in the listTools response, including name, description, and input schema.

{
  name: 'getPositionInfo',
  description: 'Get current position information.',
  inputSchema: {
    type: 'object',
    properties: {
      symbol: { type: 'string' },
    },
  },
},

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 22, 2025

TDQS

C2.4/5.0

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. It only states the action ('Get') without any details on permissions, rate limits, side effects, or response format. For a tool that likely accesses sensitive financial data, this lack of transparency is a significant gap.

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 with a single sentence ('Get current position information.'), which is front-loaded and wastes no words. For a simple tool, this brevity is appropriate, though it may contribute to the lack of detail 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 of financial position data, no annotations, no output schema, and poor parameter coverage, the description is incomplete. It doesn't address what 'current position information' includes (e.g., size, leverage, PnL) or how to interpret results, leaving the agent with insufficient context for reliable 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?

The input schema has one parameter ('symbol') with 0% description coverage, and the tool description adds no information about this parameter. It doesn't explain what 'symbol' represents (e.g., a trading pair like 'BTCUSDT'), its format, or whether it's optional (as indicated by 0 required parameters), failing to compensate for the schema's lack of documentation.

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 current position information' clearly states the verb ('Get') and resource ('current position information'), making the purpose understandable. However, it doesn't distinguish this tool from similar siblings like 'getPositionMarginHistory' or 'getPositionMode', which also retrieve position-related data, leaving some ambiguity about what specific aspect of positions is targeted.

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 siblings like 'getBalance', 'getAccountInfo', and other position-related tools, there's no indication of prerequisites, context, or exclusions, 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.