Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

getBalance

Retrieve your futures account balance to monitor trading capital and manage cryptocurrency positions on the Aster Finance exchange.

Instructions

Get futures account balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'getBalance' tool. It invokes the shared makeRequest helper to perform a signed GET request to the '/fapi/v2/balance' endpoint to retrieve the futures account balance.
    case 'getBalance':
        return makeRequest('GET', '/fapi/v2/balance', args, true);
  • src/index.ts:396-396 (registration)
    Registration of the 'getBalance' tool in the MCP server's list of tools returned by ListToolsRequestSchema. Includes the tool's name, description, and input schema (no required parameters).
    { name: 'getBalance', description: 'Get futures account balance.', inputSchema: { type: 'object', properties: {} } },
  • Input schema for 'getBalance' tool: an empty object (no parameters required).
    { name: 'getBalance', description: 'Get futures account balance.', inputSchema: { type: 'object', properties: {} } },
  • Shared helper function 'makeRequest' used by the getBalance handler (and other signed tools) to make authenticated HTTP requests to the Aster Futures API, including HMAC-SHA256 signing using API_SECRET.
    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 implies a read-only operation ('Get'), but doesn't specify authentication requirements, rate limits, error conditions, or the format of the returned balance. For a financial tool with zero annotation coverage, 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 a single, efficient sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by directly contributing to understanding the tool's function.

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 data and the absence of both annotations and an output schema, the description is insufficient. It doesn't explain what the balance includes (e.g., total, available, margin), the currency or asset format, or any behavioral traits like permissions needed. For a tool in this context, more detail is required to be complete.

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

Parameters4/5

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

The tool has 0 parameters, and the schema description coverage is 100%, so there is no need for parameter details in the description. The baseline for this scenario is 4, as the description appropriately avoids redundant information while clearly stating the tool's purpose.

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 futures account balance' clearly states the verb ('Get') and resource ('futures account balance'), making the purpose immediately understandable. It distinguishes itself from siblings like 'getAccountInfo' or 'getPositionInfo' by specifying the balance aspect of futures accounts. However, it doesn't explicitly contrast with these alternatives, preventing a perfect score.

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 like 'getAccountInfo' or 'getPositionInfo', which might also contain balance-related data. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from 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