Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

cancel_order

Cancels an existing order by specifying the order ID, enabling management of trades through the Paper MCP Server's AI-driven trading platform. Simplifies order cancellation for streamlined trade control.

Instructions

Cancel an existing order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesOrder ID to cancel

Implementation Reference

  • Handler for the cancel_order tool. Makes a PUT request to the `/orders/{orderId}/cancel` endpoint using the configured axios instance to cancel the specified order.
    case 'cancel_order':
      response = await api.put(`/orders/${args.orderId}/cancel`);
      break;
  • Input schema definition for the cancel_order tool, specifying that an orderId string is required.
      name: 'cancel_order',
      description: 'Cancel an existing order',
      inputSchema: {
        type: 'object',
        properties: {
          orderId: { type: 'string', description: 'Order ID to cancel' }
        },
        required: ['orderId']
      }
    },
  • src/index.ts:388-392 (registration)
    Registration of all tools, including cancel_order, via the ListToolsRequestSchema handler which returns the tools array containing the cancel_order tool definition.
    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 full burden for behavioral disclosure. While 'Cancel' implies a destructive mutation, it doesn't specify whether this is reversible, what permissions are required, what happens to partially filled orders, or what the response looks like. Significant behavioral details are missing.

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 appropriately sized for a simple tool and front-loads the essential action.

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 insufficient. It doesn't explain what 'cancel' entails operationally, what the expected outcome is, or any error conditions. Given the complexity and lack of structured data, 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?

Schema description coverage is 100%, so the schema already documents the single 'orderId' parameter adequately. The description adds no additional meaning about parameter usage beyond what's in the schema, meeting the baseline for high schema coverage.

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 verb ('Cancel') and resource ('an existing order'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'cancel_all_account_orders', which could cause confusion about scope.

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_all_account_orders' or when not to use it (e.g., for pending vs. executed orders). It lacks any context about prerequisites or constraints.

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