Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_transactions

Retrieve transaction history for deposits, withdrawals, orders, dividends, and fees from Trading 212 investment accounts to track financial activity and analyze portfolio performance.

Instructions

Get transaction history including deposits, withdrawals, orders, dividends, and fees

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor for fetching next page
limitNoMaximum number of results to return

Implementation Reference

  • The actual implementation of getTransactions on the client class.
    async getTransactions(params?: {
      cursor?: number;
      limit?: number;
    }): Promise<{ items: Transaction[]; nextPagePath?: string }> {
      const queryParams = new URLSearchParams();
      if (params?.cursor) queryParams.append('cursor', params.cursor.toString());
      if (params?.limit) queryParams.append('limit', params.limit.toString());
    
      const endpoint = `/equity/history/transactions${queryParams.toString() ? `?${queryParams.toString()}` : ''}`;
      const response = await this.request<{ items: unknown[]; nextPagePath?: string }>(endpoint);
    
      return {
        items: z.array(TransactionSchema).parse(response.items),
        nextPagePath: response.nextPagePath,
      };
    }
  • The MCP tool handler for 'get_transactions' which calls the client method.
    case 'get_transactions': {
      const { cursor, limit } = PaginatedInputSchema.parse(args);
      const transactions = await client.getTransactions({ cursor, limit });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(transactions, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral information. It doesn't disclose whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior beyond cursor/limit parameters, or what format the history returns. 'Get' implies safe retrieval but lacks confirmation.

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 with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core purpose immediately.

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?

For a read operation with full parameter documentation and no output schema, the description is minimally adequate but lacks important context. It doesn't explain the return format, how transaction types are distinguished, or behavioral traits like pagination or authentication needs, leaving gaps for agent understanding.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are fully documented in the schema. The description adds no additional parameter semantics beyond implying the tool returns transaction history, which is already clear from the tool name and description purpose.

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 verb ('Get') and resource ('transaction history') with specific examples of transaction types (deposits, withdrawals, orders, dividends, fees). However, it doesn't explicitly differentiate from sibling tools like get_dividends or get_order_history, which appear to fetch subsets of the same data.

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?

No guidance is provided about when to use this tool versus alternatives like get_dividends or get_order_history. The description implies comprehensive transaction retrieval but doesn't specify use cases, prerequisites, or exclusions.

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

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