Skip to main content
Glama
KyuRish

trading212-mcp-server

place_limit_order

Submit a limit order to buy or sell an instrument at a specified limit price. The order remains open until filled, cancelled, or expires, allowing you to control the execution price instead of using a market order.

Instructions

Submit a limit order that executes only when the instrument reaches your
target price. The order stays open until filled, cancelled, or expired.

Use this instead of a market order when you want to control the execution
price. Check fetch_all_orders afterward to monitor fill status.

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.
    limit_price: Maximum price to pay (buy) or minimum to accept (sell).
        For example, 150.00 means "buy at 150 or lower".
    time_validity: How long the order stays active. DAY (expires end of trading day)
        or GOOD_TILL_CANCEL (stays open until filled or manually cancelled). Defaults to DAY.

Returns:
    Order: The newly created limit order with its pending status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
quantityYes
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 provide only readOnlyHint, destructiveHint, and idempotentHint as false. The description adds behavioral context: the order stays open until filled, cancelled, or expired, and the return is a pending status order. It does not disclose potential partial fills or order book dynamics, but the given info is sufficient for safe use.

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 front-loaded with the core behavior, followed by usage guidance and parameter docs. It is concise with no wasted sentences; each line adds value. Parameter explanations are well-structured under 'Args:'.

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?

The description covers all necessary aspects: purpose, usage, parameters, return value, and monitoring advice. An output schema exists for the return type, so the description need not detail the Order structure. Complete for an agent to invoke correctly.

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?

Schema description coverage is 0%, so the description fully explains all four parameters: ticker format and validation tip, quantity sign meaning, limit_price with concrete example, and time_validity options with defaults. This adds essential meaning beyond the bare schema titles.

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 defines a limit order as executing only when the instrument reaches a target price and staying open until filled, cancelled, or expired. It explicitly distinguishes from market orders by stating 'Use this instead of a market order when you want to control the execution price.'

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

Usage Guidelines4/5

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

The description provides clear when-to-use guidance: 'Use this instead of a market order when you want to control the execution price.' It also advises monitoring fill status via fetch_all_orders and finding valid tickers via search_instrument. However, it does not explicitly contrast with stop-limit or stop orders, which are sibling tools.

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