Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_account_cash

Retrieve detailed cash balance information from Trading 212 accounts, including free, invested, blocked, and total amounts for portfolio tracking and account management.

Instructions

Get detailed cash balance information including free, invested, blocked, and total amounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'get_account_cash' calls 'client.getAccountSummary()' and returns the serialized results.
    case 'get_account_info':
    case 'get_account_cash':
    case 'get_account_summary': {
      const summary = await client.getAccountSummary();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(summary, null, 2),
          },
        ],
      };
    }
  • src/index.ts:72-80 (registration)
    Registration of the 'get_account_cash' tool in the tool definitions array.
    {
      name: 'get_account_cash',
      description:
        'Get detailed cash balance information including free, invested, blocked, and total amounts',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
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. While 'Get' implies a read operation, the description doesn't address important behavioral aspects: whether authentication is required, rate limits, whether this returns real-time or cached data, error conditions, or what format the response takes. For a financial data tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 immediately states the tool's purpose and enumerates the specific data fields returned. Every word earns its place - there's no redundancy, unnecessary elaboration, or structural issues. The information is front-loaded with no wasted verbiage.

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's moderate complexity (financial data retrieval) and the absence of both annotations and an output schema, the description is minimally adequate but incomplete. It specifies what data fields are returned but doesn't describe the response format, data types, units, or potential error conditions. For a tool that presumably returns sensitive financial information, more context about the nature and structure of the response would be helpful.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist. It earns a baseline 4 because when there are no parameters, the description shouldn't attempt to explain them, and it focuses correctly on what the tool returns instead.

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 ('detailed cash balance information'), including the specific data fields it returns (free, invested, blocked, and total amounts). It distinguishes itself from siblings like get_account_info and get_account_summary by focusing specifically on cash balances rather than general account data or summaries. However, it doesn't explicitly contrast with these siblings in the description text itself.

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_summary that likely provide overlapping or related financial data, there's no indication of when this cash-specific tool is preferable. No prerequisites, timing considerations, or exclusion criteria are mentioned.

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