Skip to main content
Glama
florinel-chis

trading212-mcp

list_instruments

Read-only

Search the full universe of tradable instruments with optional filtering by ticker, name, or type. Returns up to 17,000 instruments including stocks, ETFs, and more.

Instructions

Search the tradable instrument universe.

The API returns the full universe (roughly 17,000 instruments) in one response with no server-side filtering, so search, instrument_type, and limit are applied client-side here.

Rate limit: 1 request per 50 seconds — strict. Every call fetches the whole universe, so batch your lookups into one broad search rather than issuing several calls in quick succession.

Returns per instrument: ticker (unique T212 identifier such as "AAPL_US_EQ"; may contain "/" like "BRK/A_US_EQ"), type, name, shortName (exchange symbol, may contain dots), isin, currencyCode (ISO 4217, except "GBX" — pence — for some LSE lines), maxOpenQuantity (fractional allowed), and extendedHours (whether it trades outside the regular session).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of instruments to return
searchNoCase-insensitive substring matched against the T212 ticker (e.g. 'AAPL_US_EQ') and the instrument name (e.g. 'Apple')
instrument_typeNoFilter by instrument type (case-insensitive). Common values: STOCK, ETF, WARRANT; the API may also return CRYPTOCURRENCY, FOREX, FUTURES, INDEX, CVR, CORPACT

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Adds critical behavioral details beyond the readOnlyHint annotation: rate limit (1/50s), client-side filtering, full-universe retrieval, field-level quirks (ticker format, currency exceptions). Completely transparent.

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?

Concise 8-sentence description with clear structure: purpose, caveats, rate limit, return fields. Every sentence serves a purpose, no redundancy.

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 output schema exists and full parameter documentation, description covers all behavioral aspects: no server-side filter, rate limit, and field nuances. Fully complete for the complexity.

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 100% coverage, but description adds significant value: client-side filtering explanation, examples for search matching, common instrument_type values, and behavior of limit. Goes well beyond schema descriptions.

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 'Search the tradable instrument universe' with a specific verb and resource. It distinguishes itself from sibling tools that are all specific queries (e.g., get_order, list_orders) by being the only search tool.

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?

Explicitly explains client-side filtering and rate limit, and advises batching lookups. No sibling tool provides similar search, so no exclusion needed. Lacks explicit 'when not to use' but clear from context.

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/florinel-chis/trading212-mcp'

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