Skip to main content
Glama
RohanAnandPandit

Trading212 MCP Server

request_csv_export

Request a CSV export of account orders, dividends, and transactions history. Specify date range and data types to include.

Instructions

Request a CSV export of the account's orders, dividends and transactions
history.
Once the export is complete it can be accessed from the download link in the
 exports list.

Args:
    include_dividends: Whether to include dividend information in the export.
        Defaults to True
    include_interest: Whether to include interest information in the export.
    Defaults to True
    include_orders: Whether to include order history in the export.
    Defaults to True
    include_transactions: Whether to include transaction history in the export.
    Defaults to True
    time_from: Start time for the report in ISO 8601 format
    (e.g., '2023-01-01T00:00:00Z')
    time_to: End time for the report in ISO 8601 format
    (e.g., '2023-12-31T23:59:59Z')

Returns:
    EnqueuedReportResponse: Response containing the report ID and status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_dividendsNo
include_interestNo
include_ordersNo
include_transactionsNo
time_fromNo
time_toNo
Behavior4/5

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

No annotations are provided, but the description discloses that the export is enqueued (non-immediate) and returns a response with report ID and status. It implies the export is created asynchronously and accessed later, which is transparent for a request tool.

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?

The description is concise and structured with a clear 'Args:' section. It could be slightly more front-loaded, but each sentence adds value without unnecessary verbiage.

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?

Given no annotations and no output schema, the description covers the tool's purpose, all six parameters with explanations, and the return type. It also notes the asynchronous nature and how to access the result, making it complete.

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 compensates fully by explaining each boolean parameter's purpose and defaults, and provides ISO 8601 format examples for the time parameters. This adds significant meaning beyond the schema's titles and types.

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 verb 'Request', the resource 'CSV export', and the specific scope 'account's orders, dividends and transactions history'. It distinguishes itself from sibling tools like `fetch_exports_list` by describing the initiation of an export rather than listing them.

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 explains that after request, the export can be accessed from the exports list, providing context on the workflow. It does not explicitly state when not to use or alternatives, but the process is clear from the description.

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/RohanAnandPandit/trading212-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server