Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_position

Retrieve detailed information about a specific investment position using its ticker symbol to monitor holdings and track performance in your Trading 212 account.

Instructions

Get detailed information about a specific position by ticker symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesThe ticker symbol of the instrument (e.g., AAPL, TSLA)

Implementation Reference

  • The MCP request handler for 'get_position', which parses the ticker argument and calls the client's getPositions method.
    case 'get_position': {
      const { ticker } = TickerInputSchema.parse(args);
      const positions = await client.getPositions(ticker);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(positions, null, 2),
          },
        ],
      };
    }
  • The actual API implementation of getPositions in the Trading212Client.
    async getPositions(ticker?: string): Promise<Position[]> {
      const qs = ticker ? `?ticker=${encodeURIComponent(ticker)}` : '';
      return this.request(`/equity/positions${qs}`, {}, z.array(PositionSchema));
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention authentication needs, rate limits, error conditions, or what 'detailed information' includes (e.g., current price, holdings, performance). For a financial data tool with zero annotation coverage, this leaves significant behavioral gaps.

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 communicates the core purpose without unnecessary words. It's appropriately sized for a simple lookup tool and front-loads the essential information. Every word earns its place with zero waste.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple single-parameter input, the description is incomplete. It doesn't explain what 'detailed information' returns, authentication requirements, error handling, or how it differs from similar tools. For a financial position tool where users need to understand what data to expect, this leaves too many unanswered questions.

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%, with the single parameter 'ticker' well-documented in the schema. The description adds minimal value beyond the schema by mentioning 'ticker symbol' but provides no additional context about format requirements, valid symbols, or examples beyond what's already in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('Get detailed information') and resource ('about a specific position'), specifying it requires a ticker symbol. It distinguishes from siblings like get_instruments (general) or get_portfolio (aggregate), but doesn't explicitly name alternatives. Purpose is clear but sibling differentiation is implicit rather than explicit.

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_instruments (broader instrument info) or get_portfolio (aggregate position data). It mentions the ticker requirement but offers no context about prerequisites, appropriate scenarios, or exclusions. Usage is implied from the name and description but not explicitly stated.

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