Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_order

Retrieve detailed information about a specific Trading 212 order using its unique identifier to track status, view execution details, and monitor investment activity.

Instructions

Get detailed information about a specific order by order ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesThe unique identifier of the order

Implementation Reference

  • The tool handler logic for 'get_order' which parses the input and calls the client's getOrder method.
    case 'get_order': {
      const { orderId } = OrderIdInputSchema.parse(args);
      const order = await client.getOrder(orderId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(order, null, 2),
          },
        ],
      };
    }
  • The API client implementation that executes the HTTP request for 'get_order'.
    async getOrder(orderId: number): Promise<Order> {
      return this.request(`/equity/orders/${orderId}`, {}, OrderSchema);
    }
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. It states this is a 'get' operation, implying read-only behavior, but doesn't confirm if it's safe, whether it requires authentication, what happens with invalid IDs, or if there are rate limits. For a tool 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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads the essential information without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (single parameter, 100% schema coverage) and lack of output schema, the description is minimally adequate but has clear gaps. It doesn't explain what 'detailed information' includes or the response format, which would be helpful since there's no output schema. For a read operation with no annotations, it should provide more behavioral context.

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 'orderId' clearly documented in the schema as 'The unique identifier of the order'. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline score of 3 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 tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific order'), making it easy to understand what it does. However, it doesn't differentiate from sibling tools like 'get_orders' (plural) or 'get_order_history', which could cause confusion about when to use this versus those alternatives.

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. It doesn't mention siblings like 'get_orders' (for listing orders) or 'get_order_history' (for historical data), leaving the agent to guess based on tool names alone. There's no explicit when/when-not usage context provided.

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