Skip to main content
Glama
questflowai

Aster Finance MCP Server

by questflowai

placeBatchOrders

Execute multiple cryptocurrency trading orders simultaneously on Aster Finance to manage portfolio positions efficiently and save time on manual order placement.

Instructions

Place multiple orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batchOrdersYes

Implementation Reference

  • Executes the placeBatchOrders tool by validating the presence of batchOrders, stringifying it for the API, and making a signed POST request to the Aster futures batchOrders endpoint.
    case 'placeBatchOrders':
        if (!args || !args.batchOrders) {
            throw new McpError(ErrorCode.InvalidParams, 'batchOrders is required.');
        }
        const batchOrdersStr = JSON.stringify(args.batchOrders);
        return makeRequest('POST', '/fapi/v1/batchOrders', { ...args, batchOrders: batchOrdersStr }, true);
  • Defines the input schema and registers the placeBatchOrders tool in the listTools response, requiring a batchOrders array of order objects with symbol, side, type, and quantity.
    {
      name: 'placeBatchOrders',
      description: 'Place multiple orders.',
      inputSchema: {
        type: 'object',
        properties: {
          batchOrders: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                symbol: { type: 'string' },
                side: { type: 'string', enum: ['BUY', 'SELL'] },
                type: { type: 'string' },
                quantity: { type: 'number' },
                price: { type: 'number' },
              },
              required: ['symbol', 'side', 'type', 'quantity'],
            },
          },
        },
        required: ['batchOrders'],
      },
    },
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Place multiple orders') without any details on permissions, rate limits, side effects (e.g., financial transactions), error handling, or response format. This is inadequate for a tool that likely involves significant mutations and risks.

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 'Place multiple orders.', which is front-loaded and wastes no words. However, this conciseness comes at the cost of completeness, as it lacks necessary details for effective tool use.

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?

Given the complexity of placing multiple orders (likely involving financial transactions), no annotations, 0% schema description coverage, and no output schema, the description is severely incomplete. It does not address behavioral aspects, parameter meanings, usage context, or expected outcomes, making it inadequate for safe and effective agent operation.

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?

The input schema has 0% description coverage, and the description does not add any parameter semantics beyond the name 'batchOrders'. It fails to explain what 'batchOrders' contains (e.g., array of order objects with price, quantity, side, symbol, type) or provide context on required fields, enums, or constraints, leaving parameters largely undocumented.

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 'Place multiple orders' clearly states the verb ('Place') and resource ('orders'), but it is vague about scope and lacks differentiation from sibling tools like 'placeOrder' (which likely handles single orders). It does not specify the context (e.g., trading platform or order types), making it minimally adequate but with gaps in specificity.

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 such as 'placeOrder' for single orders or other order-related tools like 'cancelBatchOrders'. The description implies usage for batch operations but does not clarify prerequisites, constraints, or typical scenarios, leaving the agent to infer context without explicit direction.

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