t212-mcp

Single position by ticker

t212_get_position

Read-onlyIdempotent

Retrieve a specific open position from a Trading 212 account using its exact ticker (e.g., AAPL_US_EQ). Use only when the ticker is already known; otherwise, list all positions or search instruments.

Instructions

Returns one open position by its exact Trading 212 ticker (for example AAPL_US_EQ, not AAPL). Only use this when you already know the exact ticker — otherwise call t212_list_positions, which returns everything in a single request, or t212_search_instruments to resolve a name to a ticker. Fails if the account holds no such position.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "t212_get_position"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Exact Trading 212 ticker, e.g. AAPL_US_EQ. Case-sensitive.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: it fails if no position exists, clarifies that the ticker must be exact (including suffix), and implies the scope is open positions only. This enriches the agent's understanding.

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 three short sentences: the first states the action, the second provides usage guidance with alternatives, and the third notes the failure condition. Every sentence earns its place with no wasted words.

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

Completeness5/5

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

Despite having no output schema, the tool is simple and the description covers its core purpose, when to use it, and edge-case behavior. Annotations handle safety aspects, so the description is complete for effective selection and invocation.

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 fully describes the ticker parameter (100% coverage), so the baseline is 3. The description goes beyond the schema by giving a concrete example and explicitly contrasting it with the plain ticker form, adding semantic clarity that helps the agent avoid common mistakes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns one open position by exact Trading 212 ticker, and distinguishes itself from sibling tools by explicitly naming the alternatives and providing a concrete ticker example (AAPL_US_EQ, not AAPL). This is a specific verb+resource with strong sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('Only use this when you already know the exact ticker') and provides clear alternatives ('otherwise call t212_list_positions... or t212_search_instruments'). This is a textbook example of usage guidance with exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server