Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

place_limit_order

Execute buy or sell orders at a specific price or better to control trade entry and exit points in financial markets.

Instructions

Place a limit order to buy or sell at a specified price or better

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesThe ticker symbol of the instrument
quantityYesThe quantity to buy (positive) or sell (negative)
limitPriceYesThe limit price for the order
timeValidityNoTime validity of the orderDAY

Implementation Reference

  • The handler implementation for the 'place_limit_order' tool in src/index.ts. It parses arguments using LimitOrderRequestSchema and calls the client's placeLimitOrder method.
    case 'place_limit_order': {
      const validated = LimitOrderRequestSchema.parse(args);
      const order = await client.placeLimitOrder(validated);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(order, null, 2),
          },
        ],
      };
    }
  • The API client implementation of placeLimitOrder, which performs the actual HTTP POST request to the Trading 212 API.
    async placeLimitOrder(order: LimitOrderRequest): Promise<Order> {
      return this.request(
        '/equity/orders/limit',
        {
          method: 'POST',
          body: JSON.stringify(order),
        },
        OrderSchema,
      );
    }
  • src/index.ts:177-203 (registration)
    Tool registration and schema definition for 'place_limit_order'.
      name: 'place_limit_order',
      description: 'Place a limit order to buy or sell at a specified price or better',
      inputSchema: {
        type: 'object',
        properties: {
          ticker: {
            type: 'string',
            description: 'The ticker symbol of the instrument',
          },
          quantity: {
            type: 'number',
            description: 'The quantity to buy (positive) or sell (negative)',
          },
          limitPrice: {
            type: 'number',
            description: 'The limit price for the order',
          },
          timeValidity: {
            type: 'string',
            enum: ['DAY', 'GOOD_TILL_CANCEL'],
            description: 'Time validity of the order',
            default: 'DAY',
          },
        },
        required: ['ticker', 'quantity', 'limitPrice'],
      },
    },
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 of behavioral disclosure. It states the action ('place a limit order') but doesn't mention critical behaviors like authentication requirements, rate limits, whether the order is executed immediately or queued, potential side effects (e.g., account balance changes), or error handling. This leaves significant gaps for a financial transaction 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 that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse 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 complexity of a financial order placement tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., execution behavior, errors), output expectations, and usage context, leaving the agent under-informed for safe and effective invocation.

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%, providing clear documentation for all parameters (ticker, quantity, limitPrice, timeValidity). The description adds minimal value beyond the schema by implying the 'limit' aspect of the order, but it doesn't elaborate on parameter meanings, constraints, or interactions, 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 ('place a limit order') and the resource ('buy or sell at a specified price or better'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'place_market_order' or 'place_stop_limit_order', which would require mentioning the specific price condition or execution guarantee.

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 such as 'place_market_order' or 'place_stop_order'. The description implies usage for limit orders but lacks explicit context, prerequisites, or exclusions, leaving the agent to infer based on general knowledge.

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