Skip to main content
Glama
KyuRish

trading212-mcp-server

search_instrument

Read-onlyIdempotent

Search for tradeable instruments by ticker or company name to find the correct Trading 212 ticker format. Returns matching instruments with ticker, ISIN, currency, and type. Omit the search term to retrieve the full catalogue.

Instructions

Search for tradeable instruments by ticker symbol or company name.
Returns matching instruments with their ticker, ISIN, currency, and type.

Use this before placing orders or creating pies to find the correct Trading 212
ticker format (e.g., 'AAPL_US_EQ' for Apple). Omit the search term to retrieve
the full instrument catalogue.

The search is case-insensitive and matches partial strings against both
ticker symbols and instrument names.

Args:
    search_term: Text to match against tickers and names (e.g., 'Apple', 'AAPL',
        'silver ETC'). Omit to return every available instrument.

Returns:
    List of Instrument objects with ticker, name, type (STOCK/ETF), currencyCode,
    isin, shortName, and maxOpenQuantity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
search_termNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnly and idempotent hints. Description adds case-insensitivity and partial matching, complementing annotations without contradiction.

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?

Well-structured with sections, concise yet comprehensive, no redundant sentences.

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 single parameter and presence of output schema, description adequately covers behavior and return values.

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 coverage is 0%, but the description compensates by explaining search_term: a string for matching, can be omitted to return all instruments.

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 the tool searches for tradeable instruments by ticker or name, returning specific fields. It distinguishes itself from sibling tools like search_exchange by focusing on instruments.

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

Usage Guidelines4/5

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

Description specifies when to use (before orders/pies) and that omitting search_term returns full catalogue. Lacks explicit when-not-to-use or alternatives.

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