Skip to main content
Glama
KyuRish

trading212-mcp-server

place_market_order

Execute a market order at the current price to buy or sell shares immediately. Specify ticker and quantity (positive to buy, negative to sell; fractional shares supported). Requires prior instrument search and cash check.

Instructions

Execute a market order at the current price. This creates a real trade that
affects your portfolio immediately. The order fills at the best available
market price.

Use search_instrument first to find the correct ticker symbol. Check
fetch_account_cash to verify sufficient buying power before placing.

Args:
    ticker: Instrument ticker to trade (e.g., 'AAPL_US_EQ', 'MSFT_US_EQ').
        Use search_instrument to find valid tickers.
    quantity: Number of shares. Positive to buy, negative to sell.
        Fractional shares are supported (e.g., 0.5).

Returns:
    Order: The newly created order with its initial status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
quantityYes

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?

Describes that the order creates a real trade affecting the portfolio immediately and fills at best available price. Annotations are minimal (no readOnly, destructive, or idempotent hints), so description adds necessary behavioral context without contradiction.

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?

Concise, front-loaded with purpose, followed by usage guidelines, then parameter details. Every sentence adds value without redundancy.

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 all necessary aspects: purpose, prerequisites, parameter semantics, and return type. No gaps given the tool's simplicity and presence of output schema.

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?

Despite 0% schema description coverage, the parameter docs add extensive meaning: ticker format with examples and reference to search_instrument, quantity meaning with sign convention and fractional share support.

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 'Execute a market order at the current price' with specific verb and resource. Distinguishes from sibling tools like place_limit_order by implying immediacy and market price execution.

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 advises using search_instrument first to find correct ticker and checking fetch_account_cash for sufficient buying power, providing clear prerequisites and alternatives.

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