Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

place_stop_order

Execute a stop order that converts to a market order when a specified price threshold is reached, enabling automated trading decisions in Trading 212 accounts.

Instructions

Place a stop order that becomes a market order when the stop price is reached

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesThe ticker symbol of the instrument
quantityYesThe quantity to buy (positive) or sell (negative)
stopPriceYesThe stop price that triggers the market order
timeValidityNoTime validity of the orderDAY

Implementation Reference

  • The core client implementation for the place_stop_order tool, which sends a POST request to the /equity/orders/stop API endpoint.
    async placeStopOrder(order: StopOrderRequest): Promise<Order> {
      return this.request(
        '/equity/orders/stop',
        {
          method: 'POST',
          body: JSON.stringify(order),
        },
        OrderSchema,
      );
    }
  • src/index.ts:669-680 (registration)
    The registration of the place_stop_order tool handler within the MCP server's request handler switch statement.
    case 'place_stop_order': {
      const validated = StopOrderRequestSchema.parse(args);
      const order = await client.placeStopOrder(validated);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(order, null, 2),
          },
        ],
      };
    }
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 explains the basic behavior (stop order triggers a market order), but fails to disclose critical traits such as execution risks (e.g., slippage), authentication requirements, rate limits, order confirmation details, or potential errors. This is inadequate for a financial trading tool with no annotation coverage.

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 explains the tool's function without unnecessary words. It is front-loaded with the core action and mechanism, making it easy to 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 complexity of a financial order placement tool with no annotations and no output schema, the description is insufficient. It lacks details on return values (e.g., order ID or confirmation), error handling, side effects (e.g., fund holds), and behavioral nuances like order lifecycle. This leaves significant gaps for an AI agent to use the tool effectively.

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 fully documents all parameters. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't clarify the relationship between stopPrice and market execution or explain quantity sign conventions). Baseline 3 is appropriate as the schema handles parameter documentation.

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 stop order') and the mechanism ('becomes a market order when the stop price is reached'), which is specific and distinguishes it from siblings like 'place_market_order' or 'place_limit_order'. However, it doesn't explicitly mention the financial instrument context (e.g., trading stocks), though this is implied by the tool name and sibling tools.

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 such as 'place_stop_limit_order' or 'place_market_order'. It lacks context about scenarios where a stop order is appropriate (e.g., for risk management or automated trading) or prerequisites like account permissions.

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