Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

getPositionMode

Retrieve your current position mode setting for cryptocurrency futures trading on the Aster exchange to manage your trading strategy and risk exposure.

Instructions

Get user's position mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:227-227 (registration)
    Registration of the 'getPositionMode' tool in the list of tools provided by ListToolsRequestSchema handler, including its schema (empty object input).
    { name: 'getPositionMode', description: "Get user's position mode.", inputSchema: { type: 'object', properties: {} } },
  • Input schema for getPositionMode tool: empty object.
    { name: 'getPositionMode', description: "Get user's position mode.", inputSchema: { type: 'object', properties: {} } },
  • Handler implementation in the switch statement within CallToolRequestSchema: performs a signed GET request to Aster API endpoint '/fapi/v1/positionSide/dual' using the shared makeRequest function.
    case 'getPositionMode':
        return makeRequest('GET', '/fapi/v1/positionSide/dual', args, true);
  • Shared helper function used by all signed tool handlers, including getPositionMode, to make authenticated API requests to Aster DEX.
    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 states it's a read operation ('Get'), implying it's non-destructive, but doesn't cover critical aspects like authentication requirements, rate limits, error conditions, or what the return data looks like (e.g., hedging vs. one-way mode). This is a significant gap for a tool with zero annotation coverage.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse, which is ideal for a simple tool like this.

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 (a read operation with no parameters but likely requiring authentication) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'position mode' entails (e.g., its values or implications), how the data is returned, or any behavioral constraints, leaving the agent under-informed for proper use.

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% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline expectation. No additional value is required or provided beyond the empty 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 'Get user's position mode' clearly states the verb ('Get') and resource ('user's position mode'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'setPositionMode' or explain what 'position mode' means in this context, leaving some ambiguity about the specific function.

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. It doesn't mention prerequisites (e.g., authentication), when it's appropriate (e.g., before trading), or differentiate it from similar tools like 'getPositionInfo' or 'setPositionMode', leaving the agent with no usage context.

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