Skip to main content
Glama
KyuRish

trading212-mcp-server

fetch_historical_order_data

Read-onlyIdempotent

Retrieve past orders with execution details, fill prices, and timestamps. Filter by ticker or paginate through results to review trade history or analyze execution quality.

Instructions

Retrieve past orders (filled, cancelled, rejected) with execution details,
fill prices, and timestamps. Supports pagination and ticker filtering.

Use this to review trade history or to analyze past execution quality.
For currently active orders, use fetch_all_orders instead.

Args:
    cursor: Pagination cursor from a previous response. Omit for the first page.
    ticker: Filter results to a specific instrument (e.g., 'AAPL_US_EQ'). Omit for all.
    limit: Number of orders per page, 1-50. Defaults to 20.

Returns:
    List of HistoricalOrder with ticker, type, status, filledQuantity, fillPrice,
    dateCreated, dateExecuted, and more

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNo
tickerNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds context about pagination and ticker filtering, which are behavioral details beyond annotations. It does not contradict annotations.

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, usage, args, returns. It is front-loaded with the main purpose, and 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?

The output schema exists, and the description lists the return fields (ticker, type, status, etc.). It covers input parameters, usage guidance, and return value details, making it complete for the tool's moderate complexity.

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 no descriptions (0% coverage), but the description explains each parameter: cursor for pagination, ticker for filtering, limit for page size with defaults and constraints (1-50, default 20). This fully compensates for the missing schema descriptions.

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 the tool retrieves past orders with execution details, fill prices, and timestamps. It explicitly distinguishes itself from fetch_all_orders for active orders, providing a specific verb-resource pairing.

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 the tool ('review trade history', 'analyze past execution quality') and when not to ('For currently active orders, use fetch_all_orders'). This provides clear usage context and a sibling alternative.

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