Skip to main content
Glama
KyuRish

trading212-mcp-server

place_stop_limit_order

Place a stop-limit order to automatically trigger a limit order when a specified stop price is reached, preventing unfavorable execution during fast market moves while maintaining price control.

Instructions

Submit a combined stop-limit order: once the stop price is hit, a limit order
is placed at your specified limit price instead of executing at market.

This gives more control than a plain stop order by preventing execution at
an unfavourable price during fast market moves, but the order may not fill
if the price moves through the limit. See also: place_stop_order for a
simpler stop that guarantees execution.

Args:
    ticker: Instrument ticker (e.g., 'AAPL_US_EQ'). Use search_instrument to find valid tickers.
    quantity: Number of shares. Positive to buy, negative to sell.
    stop_price: Trigger price that activates the limit order (e.g., 140.00).
    limit_price: Price at which the resulting limit order is placed (e.g., 139.50).
        Typically set slightly below the stop price for sells.
    time_validity: DAY or GOOD_TILL_CANCEL. Defaults to DAY.

Returns:
    Order: The newly created stop-limit order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
quantityYes
stop_priceYes
limit_priceYes
time_validityNoDAY

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
tickerYes
typeNo
statusNo
quantityNo
filledQuantityNo
filledValueNo
limitPriceNo
stopPriceNo
strategyNo
valueNo
creationTimeNo
Behavior4/5

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

Annotations show readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description discloses that the tool creates an order (mutation), explains the non-fill risk, and contrasts with market execution. It doesn't mention auth or rate limits, but the annotations provide sufficient baseline, and the description adds useful context.

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 concise with a clear structure: purpose statement, benefits, risk, alternative, then args in bullet-like format, then return type. Every sentence adds value; no wasted words.

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

Completeness4/5

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

Given the tool has an output schema (Order), the description doesn't need to detail return values. It covers purpose, usage, parameters, and behavior adequately. Could mention idempotency or side effects (e.g., multiple submissions create multiple orders), but overall it's quite complete.

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

Parameters5/5

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

The input schema has 5 parameters with 0% description coverage. The description adds full semantic context: ticker example and lookup hint, quantity direction (positive/negative), stop_price, limit_price tip for sells, and time_validity default. Schema provides types but description adds meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it submits a stop-limit order, explains the mechanism ('once the stop price is hit, a limit order is placed'), and distinguishes it from a plain stop order. It also mentions specific parameters and returns an Order.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('gives more control than a plain stop order') and names the alternative ('See also: place_stop_order'). It also warns about the risk of non-fill if the price moves through the limit.

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

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