Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_instruments

Retrieve tradeable instruments with metadata like ISIN, currency, and trading schedules to identify available assets for investment and trading decisions.

Instructions

List all tradeable instruments with metadata including ISIN, currency, type, and trading schedules

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoOptional search query to filter instruments by ticker, name, or ISIN

Implementation Reference

  • The handler for 'get_instruments' which processes the request, calls the client, and filters the result.
    case 'get_instruments': {
      const { search } = SearchInputSchema.parse(args);
      let instruments = await client.getInstruments();
    
      if (search) {
        const searchLower = search.toLowerCase();
        instruments = instruments.filter(
          (i) =>
            i.ticker.toLowerCase().includes(searchLower) ||
            i.name.toLowerCase().includes(searchLower) ||
            i.shortName?.toLowerCase().includes(searchLower) ||
            i.isin?.toLowerCase().includes(searchLower),
        );
      }
    
      return {
        content: [
          {
  • src/index.ts:267-280 (registration)
    Registration of the 'get_instruments' tool.
    {
      name: 'get_instruments',
      description:
        'List all tradeable instruments with metadata including ISIN, currency, type, and trading schedules',
      inputSchema: {
        type: 'object',
        properties: {
          search: {
            type: 'string',
            description: 'Optional search query to filter instruments by ticker, name, or ISIN',
          },
        },
      },
    },
  • The client method that performs the API request to fetch instruments.
    async getInstruments(): Promise<Instrument[]> {
      return this.request('/equity/metadata/instruments', {}, z.array(InstrumentSchema));
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions metadata fields but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, rate limits, pagination, or what happens if no instruments match. For a list operation with no annotations, this leaves significant gaps in understanding how it behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('List all tradeable instruments') and adds useful metadata details. There's no wasted text, though it could be slightly more structured by separating purpose from metadata.

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 and no output schema, the description is incomplete. It doesn't explain what the return values look like (e.g., format, pagination), authentication needs, or error conditions. For a tool that lists financial instruments, more context on behavior and output is needed for effective use.

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%, so the schema already documents the optional 'search' parameter. The description doesn't add any parameter-specific information beyond implying a list operation. It mentions metadata fields but doesn't tie them to parameters. Baseline 3 is appropriate since the schema handles parameter documentation.

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 verb ('List') and resource ('all tradeable instruments'), specifying the scope ('all') and metadata details (ISIN, currency, type, trading schedules). It distinguishes from siblings like get_exchanges (which lists exchanges) or get_account_info (which focuses on account data).

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention if this should be used for general browsing versus get_position for specific holdings, or how it relates to get_exchanges for exchange-specific instruments. The description only states what it does, not when to choose it.

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