Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

cancel_all_account_orders

Cancel all active orders for a specific account on Paper's trading platform using this tool. Provide the account ID to execute the action and manage trading activities efficiently.

Instructions

Cancel all orders for an account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesAccount ID

Implementation Reference

  • Handler implementation for the 'cancel_all_account_orders' tool. Executes a DELETE API request to `/orders/account/${accountId}` to cancel all open orders for the specified account.
    case 'cancel_all_account_orders':
      response = await api.delete(`/orders/account/${args.accountId}`);
      break;
  • Tool definition including name, description, and input schema requiring 'accountId'.
    {
      name: 'cancel_all_account_orders',
      description: 'Cancel all orders for an account',
      inputSchema: {
        type: 'object',
        properties: {
          accountId: { type: 'string', description: 'Account ID' }
        },
        required: ['accountId']
      }
    },
  • src/index.ts:388-392 (registration)
    Registration of all tools list, which includes 'cancel_all_account_orders' via the 'tools' array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools
      };
    });
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. While 'Cancel all orders' clearly indicates a destructive mutation, it doesn't specify whether this action is reversible, what permissions are required, whether there are rate limits, or what happens to partially filled orders. For a destructive operation with zero annotation coverage, 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 extremely concise - a single six-word sentence that directly states the tool's purpose with zero wasted words. It's perfectly front-loaded and efficiently communicates the core functionality.

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?

For a destructive mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after cancellation (confirmation? error handling?), what types of orders are affected, or any constraints on when this operation can be performed. Given the complexity of financial order management, more context is needed.

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 schema description coverage is 100%, with the single parameter 'accountId' clearly documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema, so it meets the baseline for high schema coverage without providing additional semantic context.

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 clearly states the action ('Cancel all orders') and the target resource ('for an account'), providing a specific verb+resource combination. However, it doesn't differentiate from the sibling 'cancel_order' tool, which presumably cancels individual orders rather than all orders for an account.

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 'cancel_order' or 'get_account_orders'. There's no mention of prerequisites, exclusions, or specific contexts where this tool is appropriate versus other order management tools.

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