Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

setLeverage

Adjust trading leverage for cryptocurrency positions on Aster Finance. Modify risk exposure by setting leverage ratios between 1x and 125x for specific trading pairs.

Instructions

Change user's initial leverage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leverageYes
symbolYes

Implementation Reference

  • src/index.ts:398-409 (registration)
    Registration of the 'setLeverage' tool in the ListToolsRequestHandler, defining its name, description, and input schema (symbol and leverage).
    {
      name: 'setLeverage',
      description: "Change user's initial leverage.",
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          leverage: { type: 'number', minimum: 1, maximum: 125 },
        },
        required: ['symbol', 'leverage'],
      },
    },
  • Input schema definition for the setLeverage tool, specifying required parameters: symbol (string) and leverage (number between 1 and 125).
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string' },
        leverage: { type: 'number', minimum: 1, maximum: 125 },
      },
      required: ['symbol', 'leverage'],
  • Handler implementation for the setLeverage tool within the CallToolRequestHandler switch statement. It invokes the shared makeRequest function with a signed POST request to the Aster Futures API endpoint '/fapi/v1/leverage'.
    case 'setLeverage':
        return makeRequest('POST', '/fapi/v1/leverage', args, true);
  • Shared helper function 'makeRequest' used by all signed tool handlers, including setLeverage. Handles API signing with timestamp and HMAC-SHA256 signature using API_KEY and API_SECRET, makes axios request to Aster API, and formats response or throws MCP errors.
    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 full burden but only states the action without disclosing behavioral traits like permission requirements, rate limits, side effects (e.g., impact on open positions), or response format. 'Change' implies mutation but lacks critical details for safe use.

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 zero waste, front-loading the core purpose. It's appropriately sized for a simple tool, though brevity contributes to gaps 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 no annotations, 0% schema coverage, no output schema, and a mutation tool with 2 parameters, the description is incomplete. It lacks details on behavior, parameters, output, and usage context, making it inadequate for safe and effective tool selection.

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 but adds no parameter semantics. It doesn't explain what 'symbol' or 'leverage' represent, their formats, or constraints (e.g., leverage range 1-125 from schema). This leaves parameters largely undocumented.

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 clearly states the action ('Change') and target ('user's initial leverage'), which is specific and unambiguous. However, it doesn't differentiate from siblings like 'setMarginType' or 'setMultiAssetsMode' that also modify account settings, leaving some ambiguity about scope.

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 like 'setMarginType' or 'modifyPositionMargin', nor any prerequisites or context for leverage changes. The description lacks explicit when/when-not instructions or sibling comparisons.

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