Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

placeOrder

Execute cryptocurrency trades on Aster Finance by submitting buy or sell orders with various order types including limit, market, stop, and take profit orders.

Instructions

Send in a new order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
positionSideNo
priceNo
quantityNo
sideYes
stopPriceNo
symbolYes
timeInForceNo
typeYes

Implementation Reference

  • Handler for the 'placeOrder' tool: executes a signed POST request to the Aster API endpoint '/fapi/v1/order' using the shared makeRequest function with the provided arguments.
    case 'placeOrder':
        return makeRequest('POST', '/fapi/v1/order', args, true);
  • Input schema for the 'placeOrder' tool, defining parameters such as symbol, side, type, quantity, price, etc., with required fields.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string' },
        side: { type: 'string', enum: ['BUY', 'SELL'] },
        positionSide: { type: 'string', enum: ['BOTH', 'LONG', 'SHORT'] },
        type: { type: 'string', enum: ['LIMIT', 'MARKET', 'STOP', 'STOP_MARKET', 'TAKE_PROFIT', 'TAKE_PROFIT_MARKET', 'TRAILING_STOP_MARKET'] },
        timeInForce: { type: 'string', enum: ['GTC', 'IOC', 'FOK', 'GTX'] },
        quantity: { type: 'number' },
        price: { type: 'number' },
        stopPrice: { type: 'number' },
      },
      required: ['symbol', 'side', 'type'],
    },
  • src/index.ts:240-257 (registration)
    Registration of the 'placeOrder' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'placeOrder',
      description: 'Send in a new order.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string' },
          side: { type: 'string', enum: ['BUY', 'SELL'] },
          positionSide: { type: 'string', enum: ['BOTH', 'LONG', 'SHORT'] },
          type: { type: 'string', enum: ['LIMIT', 'MARKET', 'STOP', 'STOP_MARKET', 'TAKE_PROFIT', 'TAKE_PROFIT_MARKET', 'TRAILING_STOP_MARKET'] },
          timeInForce: { type: 'string', enum: ['GTC', 'IOC', 'FOK', 'GTX'] },
          quantity: { type: 'number' },
          price: { type: 'number' },
          stopPrice: { type: 'number' },
        },
        required: ['symbol', 'side', 'type'],
      },
    },
  • Shared helper function 'makeRequest' that performs authenticated HTTP requests to the Aster API, used by the placeOrder handler for signed POST requests.
    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;
      }
    };
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but offers zero behavioral information. It doesn't disclose that this is a destructive/mutative operation (placing an order), doesn't mention authentication requirements, rate limits, or what happens on execution. The description is completely inadequate for a financial trading tool.

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 at just 4 words. While this brevity reflects severe under-specification, the text itself is not verbose or poorly structured - it's just incomplete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex financial trading tool with 8 parameters, no annotations, 0% schema coverage, and no output schema, the description is completely inadequate. It provides no meaningful context about what the tool does, how to use it, what parameters mean, or what behavior to expect.

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

Parameters1/5

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

Schema description coverage is 0%, meaning all 8 parameters are undocumented in the schema. The description provides no information about any parameters - not even mentioning the 3 required ones (symbol, side, type). It fails to compensate for the complete lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Send in a new order' restates the tool name 'placeOrder' without adding specificity. It uses a vague verb 'send in' rather than clearly stating it creates/submits an order, and doesn't distinguish this from sibling tools like 'placeBatchOrders' or 'cancelOrder'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives. There's no mention of prerequisites, when to choose this over 'placeBatchOrders', or what context requires this single-order submission tool.

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