Aster Finance MCP Server

getLeverageBrackets

Retrieve notional and leverage brackets for cryptocurrency trading positions to manage risk and margin requirements on the Aster exchange.

Instructions

Get notional and leverage brackets.

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": "getLeverageBrackets"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	No

Implementation Reference

src/index.ts:679-680 (handler)
The handler logic for the 'getLeverageBrackets' tool. It invokes a signed GET request to the Binance Futures API endpoint '/fapi/v1/leverageBracket' using the generic makeRequest function.
```
case 'getLeverageBrackets':
    return makeRequest('GET', '/fapi/v1/leverageBracket', args, true);
```
src/index.ts:493-498 (schema)
Input schema for the 'getLeverageBrackets' tool, defining 'symbol' as a required string property.
```
inputSchema: {
  type: 'object',
  properties: {
    symbol: { type: 'string' },
  },
},
```

src/index.ts:490-499 (registration)

Registration of the 'getLeverageBrackets' tool in the tools list provided to the MCP server.setTools method.

{
  name: 'getLeverageBrackets',
  description: 'Get notional and leverage brackets.',
  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

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 implies a read-only operation ('Get'), but doesn't specify if it requires authentication, has rate limits, returns real-time or historical data, or what happens on errors. For a financial tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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

Conciseness4/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('Get'), but could be slightly improved by adding minimal context to enhance clarity without losing conciseness.

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 tools, no annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't explain the return format, error handling, or how the data integrates with other tools like 'setLeverage,' leaving the agent with insufficient context for effective 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 doesn't mention parameters at all. It fails to compensate for the low schema coverage by explaining what 'symbol' represents (e.g., a trading pair like BTCUSDT) or if it's optional. With undocumented parameters, the description adds no value beyond the 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 states the tool retrieves 'notional and leverage brackets,' which clarifies it's a read operation for financial data. However, it's vague about what these brackets represent (e.g., trading limits, margin requirements) and doesn't distinguish it from siblings like 'getAccountInfo' or 'getPositionInfo,' which might overlap in financial data retrieval. It avoids tautology by specifying the data type beyond the name.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'getAccountInfo' and 'getPositionInfo' that might offer related financial data, the description lacks context on prerequisites, such as needing a specific symbol or account setup, and doesn't mention exclusions or recommend other tools for different needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.