Skip to main content
Glama

Search ETFs

SearchEtfs
Read-only

Search active exchange-traded funds and products by ticker, fund name, sponsor, or ISIN, US and other exchanges. US ETF identity comes from the authoritative security-type reference directory, with assets and holdings from the linked SEC Form NPORT-P fund series when available; a fund listed on another exchange is named MIC:TICKER (for example XETR:SXR8) with its currency and ISIN. US matches come first. Use GetEtfProfile for analysis, GetStockPrices for a fund's price history, or GetEtfHoldings for the portfolio.

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": {
      "query": "<query>"
    },
    "name": "SearchEtfs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTicker, fund name, sponsor, or ISIN (for example SPY, S&P 500, iShares, SXR8, or IE00B5BMR087).
exchangeNoMarket identifier code of one exchange outside the US to search alone (for example XETR); omit to search the US first, then other exchanges.
maxResultsNoMaximum results to return (default 20, max 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / exchange
      Added value: +{
      +  "default": null,
      +  "description": "Market identifier code of one exchange outside the US to search alone (for example XETR); omit to search the US first, then other exchanges.",
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Ticker, fund name, or sponsor (for example SPY, S&P 500, or iShares)."New value: +"Ticker, fund name, sponsor, or ISIN (for example SPY, S&P 500, iShares, SXR8, or IE00B5BMR087)."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only and non-destructive, but the description adds provenance (security-type reference directory, NPORT-P series), non-US naming as MIC:TICKER with currency/ISIN, and US-first ordering. It does not discuss pagination, rate limits, or full result shape, so it is strong but not exhaustive.

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 purpose and scope are front-loaded, and later sentences add provenance, naming, ordering, and alternatives without filler. It is a dense paragraph rather than a bulleted structure, but no sentence is clearly dispensable.

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

Completeness4/5

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

For a three-parameter, read-only search tool with no output schema, the description covers source authority, geographic behavior, result naming, ordering, and sibling alternatives well. It still leaves result fields and pagination behavior implicit.

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 coverage is 100%, so the baseline is 3; query categories and maxResults are already fully documented. The description adds only limited parameter-level meaning, mainly the MIC:TICKER naming and US-first ordering for the exchange scope, while not expanding maxResults or exchange code semantics beyond the 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?

The description states a specific verb (Search), resource (active ETFs/products), searchable attributes (ticker, fund name, sponsor, ISIN), and US/non-US scope. It also explicitly routes analysis, price-history, and holdings use cases to named alternatives, making its role distinguishable from key siblings.

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?

It gives clear routing for GetEtfProfile, GetStockPrices, and GetEtfHoldings, so the agent knows which sibling to choose for adjacent tasks. It does not address when to prefer this over other search siblings such as SearchFunds, nor state exclusions beyond the ETF/active scope.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.