Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

cancel_order

Cancel an active trading order by its unique ID to manage positions and control investment execution.

Instructions

Cancel an active order by order ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesThe unique identifier of the order to cancel

Implementation Reference

  • The core implementation that sends the DELETE request to the server to cancel an order.
    async cancelOrder(orderId: number): Promise<void> {
      await this.request(`/equity/orders/${orderId}`, {
        method: 'DELETE',
      });
    }
  • The MCP tool handler logic that validates input and calls the client implementation.
    case 'cancel_order': {
      const { orderId } = OrderIdInputSchema.parse(args);
      await client.cancelOrder(orderId);
      return {
        content: [
          {
            type: 'text',
            text: `Order ${orderId} cancelled successfully`,
          },
        ],
      };
  • Input validation schema for the cancel_order tool.
    const OrderIdInputSchema = z.object({
      orderId: z.number(),
    });
  • src/index.ts:139-147 (registration)
    MCP tool registration for cancel_order.
    {
      name: 'cancel_order',
      description: 'Cancel an active order by order ID',
      inputSchema: {
        type: 'object',
        properties: {
          orderId: {
            type: 'number',
            description: 'The unique identifier of the order to cancel',
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Cancel an active order', implying a destructive mutation, but lacks details on permissions needed, side effects (e.g., fees, notifications), rate limits, or response behavior (e.g., confirmation message). This is a significant gap for a mutation 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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose, making it easy to scan and understand quickly.

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 tool's complexity (a destructive mutation with no annotations and no output schema), the description is incomplete. It lacks behavioral details (e.g., what 'cancel' entails, error conditions), usage context, and output expectations, leaving gaps for an AI agent to invoke it correctly.

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%, with the parameter 'orderId' fully documented in the schema as 'The unique identifier of the order to cancel'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets 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 action ('Cancel') and target resource ('an active order'), specifying it's done by order ID. It distinguishes from siblings like 'get_order' (read) and 'place_*' orders (create), but doesn't explicitly differentiate from other cancellation-related tools (none present in siblings).

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. It doesn't mention prerequisites (e.g., order must be active), exclusions (e.g., cannot cancel filled orders), or comparisons to other order-related tools like 'get_order' to check status first.

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/enderekici/trading212-mcp'

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