Trading 212 MCP Server

get_orders

Retrieve all active orders including pending and processing orders from your Trading 212 investment account for portfolio tracking and management.

Instructions

Retrieve all active orders (pending, processing, etc.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_orders"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/index.ts:605-615 (handler)

Handler for 'get_orders' MCP tool in src/index.ts. Calls client.getOrders().

case 'get_orders': {
  const orders = await client.getOrders();
  return {
    content: [
      {
        type: 'text',
        text: JSON.stringify(orders, null, 2),
      },
    ],
  };
}

src/client.ts:153-155 (handler)
Implementation of getOrders() in client.ts. Fetches orders from the /equity/orders endpoint.
```
async getOrders(): Promise<Order[]> {
  return this.request('/equity/orders', {}, z.array(OrderSchema));
}
```

src/index.ts:117-124 (registration)

Registration of 'get_orders' tool in the tool list in src/index.ts.

{
  name: 'get_orders',
  description: 'Retrieve all active orders (pending, processing, etc.)',
  inputSchema: {
    type: 'object',
    properties: {},
  },
},

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Mar 19, 2026

TDQS

B3.3/5.0

Behavior2/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. It mentions retrieving 'all active orders' but does not disclose behavioral traits such as pagination, rate limits, authentication needs, or what 'active' precisely entails (e.g., statuses included). This leaves significant gaps for a tool that likely returns multiple items.

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 is front-loaded with the core purpose and includes a clarifying parenthetical. Every word earns its place.

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 no annotations, no output schema, and a tool that retrieves multiple items, the description is incomplete. It lacks details on return format (e.g., list structure, fields), pagination, error handling, or how 'active' is defined, which are critical for an AI agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds no parameter information, which is acceptable here, but a baseline of 4 is given since it doesn't need to compensate for any schema gaps.

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 ('Retrieve') and resource ('all active orders'), specifying the scope with 'active orders (pending, processing, etc.)'. It distinguishes from siblings like 'get_order' (singular) and 'get_order_history' (historical), but could be more explicit about the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving active orders only, but does not explicitly state when to use this tool versus alternatives like 'get_order' (for a specific order) or 'get_order_history' (for past orders). No guidance on prerequisites or exclusions is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.