Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

create_batch_orders

Streamline trading by generating multiple orders simultaneously in the Paper trading platform using a single request, enabling efficient portfolio management and trade execution.

Instructions

Create multiple orders at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ordersYesArray of order objects

Implementation Reference

  • Handler implementation for the 'create_batch_orders' tool. It extracts the 'orders' array from input arguments and sends a POST request to the '/orders/batch' API endpoint.
    case 'create_batch_orders':
      response = await api.post('/orders/batch', args.orders);
      break;
  • Schema definition for the 'create_batch_orders' tool, including input validation for an array of order objects requiring portfolioId, symbol, quantity, side, and type.
    {
      name: 'create_batch_orders',
      description: 'Create multiple orders at once',
      inputSchema: {
        type: 'object',
        properties: {
          orders: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                portfolioId: { type: 'string' },
                symbol: { type: 'string' },
                quantity: { type: 'number' },
                side: { type: 'string' },
                type: { type: 'string' }
              }
            },
            description: 'Array of order objects'
          }
        },
        required: ['orders']
      }
    },
  • src/index.ts:388-392 (registration)
    Registration of all tools, including 'create_batch_orders', via the ListToolsRequestSchema handler which returns the tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools
      };
    });
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. 'Create multiple orders at once' implies a write operation but fails to mention critical aspects like permissions required, whether orders are executed immediately or queued, error handling for partial failures, rate limits, or confirmation of success. This leaves significant behavioral gaps.

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 with zero wasted words. It's front-loaded with the core action and resource, making it highly concise and well-structured for quick understanding.

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 batch order creation tool (a write operation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits, usage context, and expected outcomes, failing to compensate for the missing structured data, which is inadequate for such a tool.

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 input schema has 100% description coverage, with the 'orders' parameter documented as 'Array of order objects'. The description adds no additional meaning beyond this, such as explaining order object fields or constraints. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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 'Create multiple orders at once' clearly states the verb ('create') and resource ('orders'), with the qualifier 'multiple at once' distinguishing it from the sibling 'create_order'. However, it doesn't specify what type of orders (e.g., trading orders) or the system context, leaving some ambiguity compared to a perfect 5.

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 like 'create_order' or other order-related tools. It lacks context about batch size limits, prerequisites, or scenarios where batch creation is preferred over individual orders, offering minimal usage 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

Related 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/paperinvest/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server