Trading 212 MCP Server

get_exchanges

Retrieve exchange details and trading schedules to plan investment timing and manage portfolio activities across global markets.

Instructions

Get information about exchanges and their trading schedules

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_exchanges"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/index.ts:721-731 (handler)

The MCP handler for the "get_exchanges" tool, which delegates to the Trading212Client.

case 'get_exchanges': {
  const exchanges = await client.getExchanges();
  return {
    content: [
      {
        type: 'text',
        text: JSON.stringify(exchanges, null, 2),
      },
    ],
  };
}

src/client.ts:216-218 (handler)
The implementation of the getExchanges method in the Trading212Client which performs the API request.
```
async getExchanges(): Promise<Exchange[]> {
  return this.request('/equity/metadata/exchanges', {}, z.array(ExchangeSchema));
}
```

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Mar 19, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't specify aspects like whether it requires authentication, returns real-time or cached data, handles errors, or has rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's front-loaded and every word contributes to understanding, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 0 parameters, no annotations, and no output schema, the description is minimally complete for a simple read operation. It clarifies what information is retrieved, but lacks details on output format, error handling, or integration with siblings, leaving room for improvement in a broader context.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't mention any parameters, which is appropriate since none exist. It adds no semantic details beyond the schema, but with zero parameters, the baseline is 4 as it doesn't need to compensate for missing information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('exchanges and their trading schedules'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'get_instruments' or 'get_account_info', which also retrieve information but about different resources, so it misses full sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_instruments' (which might list tradable assets on exchanges) and 'get_account_info' (which could include exchange-related account details), there's no indication of context, prerequisites, or exclusions for selecting this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.