Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

setPositionMode

Switch between Hedge Mode and One-way Mode to manage cryptocurrency futures trading positions on the Aster exchange.

Instructions

Change user's position mode (Hedge Mode or One-way Mode).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dualSidePositionYes"true" for Hedge Mode; "false" for One-way Mode

Implementation Reference

  • Handler logic for the 'setPositionMode' tool. It invokes a signed POST request to the Aster Futures API endpoint '/fapi/v1/positionSide/dual' with the provided arguments to change the user's position mode.
    case 'setPositionMode':
        return makeRequest('POST', '/fapi/v1/positionSide/dual', args, true);
  • Input schema definition for the 'setPositionMode' tool, specifying the 'dualSidePosition' parameter as a required string.
    inputSchema: {
      type: 'object',
      properties: {
        dualSidePosition: { type: 'string', description: '"true" for Hedge Mode; "false" for One-way Mode' },
      },
      required: ['dualSidePosition'],
    },
  • src/index.ts:216-226 (registration)
    Registration of the 'setPositionMode' tool in the list of available tools, including name, description, and input schema.
    {
      name: 'setPositionMode',
      description: "Change user's position mode (Hedge Mode or One-way Mode).",
      inputSchema: {
        type: 'object',
        properties: {
          dualSidePosition: { type: 'string', description: '"true" for Hedge Mode; "false" for One-way Mode' },
        },
        required: ['dualSidePosition'],
      },
    },
  • Shared utility function 'makeRequest' used by all signed tools, including setPositionMode, to perform authenticated API calls to the Aster Futures API using HMAC-SHA256 signature.
    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 indicates a mutation ('Change'), implying potential side effects, but does not specify required permissions, rate limits, confirmation prompts, or error conditions. This leaves significant gaps for a tool that modifies user settings.

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 that directly states the tool's purpose without redundancy or unnecessary details. It is front-loaded and wastes no words, making it easy to parse quickly.

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 a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral aspects (e.g., safety, permissions), expected outcomes, or error handling, leaving the agent with incomplete context for proper invocation.

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

Parameters3/5

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

The schema description coverage is 100%, fully documenting the single parameter 'dualSidePosition' with its values. The description adds no additional parameter semantics beyond what the schema provides, such as examples or edge cases, so it meets the baseline for high schema coverage.

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 resource ('user's position mode'), specifying the two modes (Hedge Mode or One-way Mode). It distinguishes from siblings like 'getPositionMode' (which retrieves rather than changes) and 'setLeverage' (which adjusts leverage, not position mode), but does not explicitly contrast with all siblings.

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, such as prerequisites (e.g., account permissions), timing considerations, or related tools like 'setMultiAssetsMode'. It only states what the tool does, not when it should be applied.

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