Skip to main content
Glama
KyuRish

trading212-mcp-server

fetch_order

Read-onlyIdempotent

Retrieve a pending order by its ID to check current status, fill progress, and price parameters. Use to monitor an order after placing it or to confirm it's active before cancelling.

Instructions

Retrieve a single pending order by its ID to check its current status,
fill progress, and price parameters.

Use this after placing an order to monitor its status, or before cancelling
to confirm the order is still active. See also: fetch_all_orders to list
all pending orders at once.

Args:
    order_id: Numeric order ID returned when the order was placed (e.g., 12345678)

Returns:
    Order with id, ticker, type, status, quantity, filledQuantity, limitPrice, stopPrice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes

Output Schema

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

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds no additional behavioral traits beyond mentioning the tool retrieves pending orders, which is consistent. No contradictions.

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?

Very concise, front-loaded with purpose and usage, no wasted words. Parameter and return information are clearly separated.

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?

Covers purpose, usage, parameter, and return fields. Could mention error handling, but for a simple retrieval tool it is sufficiently complete.

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

Parameters4/5

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

Schema coverage 0%, but description provides meaningful context: order_id is numeric and returned when order placed. Single parameter is fully described.

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 retrieves a single pending order by ID to check status, fill progress, and price parameters. Distinguishes from sibling fetch_all_orders which retrieves all pending orders.

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 tells when to use: after placing an order to monitor, or before cancelling to confirm active. Also points to alternative fetch_all_orders for listing all pending orders.

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