Skip to main content
Glama
KyuRish

trading212-mcp-server

search_specific_position_by_ticker

Read-onlyIdempotent

Search a specific open position by its exact ticker symbol. Returns position details like quantity, average price, current price, and P&L without fetching the full portfolio.

Instructions

Look up a single open position by its exact ticker symbol.

Use this when you need details on one specific holding without fetching the
entire portfolio. Returns the same Position data as fetch_all_open_positions
but for a single instrument.

Args:
    ticker: The exact Trading 212 ticker symbol (e.g., 'AAPL_US_EQ', 'IGLDd_EQ').
        Use search_instrument to find the correct ticker if unsure.

Returns:
    Position with ticker, quantity, averagePrice, currentPrice, ppl, and more

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
quantityYes
averagePriceYes
currentPriceYes
pplNo
fxPplNo
initialFillDateNo
pieQuantityNo
maxBuyNo
maxSellNo
frontendNo
Behavior5/5

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

Annotations indicate readOnly, non-destructive, idempotent. Description adds that it returns the same Position data as fetch_all_open_positions and lists return fields (ticker, quantity, averagePrice, etc.), providing context beyond annotations.

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?

Two paragraphs with bullet points for Args and Returns. Front-loaded with purpose. Every sentence provides value; 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?

Given one parameter and existing output schema, description covers purpose, usage, parameter details, and return fields. No gaps for a single-parameter lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% coverage, but description explains ticker format with examples ('AAPL_US_EQ', 'IGLDd_EQ') and advises using search_instrument for correct ticker. Adds substantial meaning beyond the bare schema.

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?

Description clearly states it looks up a single open position by ticker symbol. Verb 'look up' combined with resource 'position by ticker' is specific. Distinguishes from sibling 'fetch_all_open_positions' by specifying single instrument.

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?

Explicitly says 'Use this when you need details on one specific holding without fetching the entire portfolio.' Also recommends 'search_instrument' for ticker lookup when unsure.

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/KyuRish/trading212-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server