Skip to main content
Glama
KyuRish

trading212-mcp-server

place_stop_order

Place a stop order to automatically trigger a market sell or buy when the instrument reaches a specified stop price, limiting risk on existing positions.

Instructions

Submit a stop order that triggers a market execution once the instrument
reaches the specified stop price. Commonly used as a stop-loss to limit
downside risk on an existing position.

When the stop price is hit, the order becomes a market order and fills at
the best available price (which may differ from the stop price in fast markets).
For more control over the fill price, use place_stop_limit_order instead.

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 order (e.g., 140.00).
    time_validity: DAY or GOOD_TILL_CANCEL. Defaults to DAY.

Returns:
    Order: The newly created stop order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
quantityYes
stop_priceYes
time_validityNoDAY

Output Schema

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

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

Discloses that the order becomes a market order and may fill at a price different from the stop price in fast markets, adding critical behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections, but slightly verbose. Could be tightened slightly without losing clarity.

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

Completeness5/5

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

Covers inputs, behavioral notes, and alternative tool. Output schema exists, so return value explanation is not needed. Comprehensive for a stop order tool.

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?

With 0% schema description coverage, the description provides detailed parameter explanations in the 'Args:' section, including example for ticker, sign convention for quantity, and default for time_validity.

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?

Clearly states it submits a stop order that becomes a market order at a specified stop price, commonly used as a stop-loss. Distinguishes from sibling tools like place_stop_limit_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?

Explicitly states common use case (stop-loss) and advises using place_stop_limit_order when more control over fill price is needed, providing clear when-to and when-not-to.

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