Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_account_info

Retrieve account metadata including currency code and account ID for Trading 212 investment accounts to enable portfolio tracking and account management.

Instructions

Retrieve account metadata including currency code and account ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler block that executes the 'get_account_info' tool (along with related account tools) using the client.getAccountSummary() method.
    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:64-71 (registration)
    The definition and registration of the 'get_account_info' tool within the tools array.
    {
      name: 'get_account_info',
      description: 'Retrieve account metadata including currency code and account ID',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The 'getAccountSummary' method in the Trading212Client class, which performs the actual API call to retrieve the account information.
    async getAccountSummary(): Promise<AccountSummary> {
      return this.request('/equity/account/summary', {}, AccountSummarySchema);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Retrieve') but doesn't address permissions, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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 with the core action and resource, making it easy to parse quickly. Every word earns its place by contributing essential information.

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 simplicity (0 parameters, no output schema, no annotations), the description is adequate for a basic read operation. It specifies what data is retrieved, which helps the agent understand the return value. However, it lacks details on behavioral aspects like error handling or format, leaving some context gaps despite the low complexity.

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, and schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't discuss parameters, focusing instead on the returned data. This meets the baseline for tools with no parameters, as there's nothing to compensate for or add beyond the 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 verb ('Retrieve') and resource ('account metadata'), specifying what data is returned ('currency code and account ID'). It distinguishes this from siblings like 'get_account_cash' or 'get_account_summary' by focusing on metadata rather than financial details. However, it doesn't explicitly contrast with all siblings, keeping it from a perfect score.

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 like 'get_account_summary' or 'get_account_cash'. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage based on tool names alone. This minimal guidance is insufficient for optimal tool selection.

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