Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_account_summary

Retrieve your Trading 212 account overview including cash balance, invested amounts, profit/loss status, and available funds for investment decisions.

Instructions

Get comprehensive account summary with cash, invested amounts, profit/loss, and available funds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the getAccountSummary method in the Trading212Client class, which makes the API call.
    async getAccountSummary(): Promise<AccountSummary> {
      return this.request('/equity/account/summary', {}, AccountSummarySchema);
    }
  • src/index.ts:82-89 (registration)
    The tool definition/registration for get_account_summary in the MCP server.
      name: 'get_account_summary',
      description:
        'Get comprehensive account summary with cash, invested amounts, profit/loss, and available funds',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The MCP request handler logic that calls the client method for get_account_summary.
    case 'get_account_summary': {
      const summary = await client.getAccountSummary();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(summary, null, 2),
          },
        ],
      };
    }
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 data ('Get'), implying a read-only operation, but doesn't mention any behavioral traits such as authentication requirements, rate limits, or potential side effects. This leaves gaps in understanding how the tool behaves in practice.

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 a single, efficient sentence that front-loads the core purpose and lists key data points without unnecessary details. It avoids redundancy and wastes no words, making it easy to scan and understand quickly.

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 and no output schema, the description adequately covers the purpose and return data. However, with no annotations and multiple sibling tools, it lacks context on usage differentiation and behavioral aspects, making it minimally viable but incomplete for optimal agent decision-making.

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, so no parameter documentation is needed. The description appropriately focuses on what the tool returns rather than inputs, adding value by specifying the data included in the summary (cash, invested amounts, etc.), which compensates for the lack of an output schema.

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 ('account summary'), and lists the key data points returned (cash, invested amounts, profit/loss, available funds). However, it doesn't explicitly differentiate from sibling tools like 'get_account_info' or 'get_account_cash', which could provide overlapping or related information.

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_account_info' and 'get_account_cash', there's no indication of how this tool differs in scope or when it's preferred over other account-related tools, leaving usage context unclear.

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