Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

setMarginType

Change margin type for cryptocurrency trading positions between isolated and crossed modes to manage risk exposure on Aster Finance exchange.

Instructions

Change margin type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marginTypeYes
symbolYes

Implementation Reference

  • The handler logic for the 'setMarginType' tool. It makes a signed POST request to the Aster API endpoint '/fapi/v1/marginType' with the provided arguments.
    case 'setMarginType':
        return makeRequest('POST', '/fapi/v1/marginType', args, true);
  • src/index.ts:410-421 (registration)
    Registration of the 'setMarginType' tool in the listTools response, including its description and input schema definition.
    {
      name: 'setMarginType',
      description: 'Change margin type.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          marginType: { type: 'string', enum: ['ISOLATED', 'CROSSED'] },
        },
        required: ['symbol', 'marginType'],
      },
    },
  • Input schema for the 'setMarginType' tool, defining parameters: symbol (string) and marginType (string, enum: ['ISOLATED', 'CROSSED']).
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string' },
        marginType: { type: 'string', enum: ['ISOLATED', 'CROSSED'] },
      },
      required: ['symbol', 'marginType'],
    },
  • Shared helper function 'makeRequest' used by the setMarginType handler (and others) to perform API requests to Asterdex, handling signing with API key/secret for authenticated endpoints.
    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. 'Change margin type.' implies a mutation operation but doesn't specify permissions required, whether it's reversible, potential risks (e.g., liquidation), rate limits, or response format. This is inadequate for a tool that likely modifies account/trading 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 extremely concise with a single sentence, front-loaded and zero waste. It efficiently communicates the core action without unnecessary words, though this 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 the tool's complexity (mutating margin settings), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It fails to address critical aspects like behavioral context, parameter meanings, or expected outcomes, making it insufficient for safe and effective use by an agent.

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 information. It doesn't explain what 'symbol' represents (e.g., trading pair) or the meaning of 'marginType' values (ISOLATED vs. CROSSED), leaving both parameters semantically unclear beyond the enum list in 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 'Change margin type.' clearly states the action (change) and resource (margin type), providing a basic purpose. However, it lacks specificity about what margin type refers to (e.g., for trading positions) and doesn't distinguish it from siblings like setLeverage or setPositionMode, which are related but distinct margin/position management tools.

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., needing an open position), exclusions, or compare it to siblings like setMultiAssetsMode or modifyPositionMargin, leaving the agent to infer usage from context 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