Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_get_etf_holdings

Fetch an ETF's constituents, holding weights, and sector mix, heaviest first, for one ticker or a comma-separated list of up to 50; use it to inspect ETF composition or confirm whether a ticker is an ETF.

Instructions

Returns an ETF's constituents and their weights, heaviest first, and its sector weights, for one ETF or a comma list of up to 50. Returns data.holdings and the sector mix data.sectors. When the ticker is not an ETF, data.is_etf is false and both are empty; data.is_etf: true with zero holdings means a real ETF whose holdings are not ingested yet. The reverse lookup ("which ETFs hold NVDA") is the etf_holders signal on tickerbot_get_ticker, or a scan: 'SMH' = ANY(etf_holders).

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": {
      "ticker": "<ticker>"
    },
    "name": "tickerbot_get_etf_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHoldings per page, per ETF. Max 5000 until 2027-01-12, then 1000 (an over-cap `limit` is clamped to the max, not an error; see Deprecations). When more holdings follow the page, the ETF's object carries `truncated: true` and `total` (its full holding count), and `next_cursor` pages the rest.
cursorNoContinue paging: the previous response's `next_cursor`, unchanged. Send it with the same params as the first page (`limit` may change); a page whose params differ is a 400 naming the param. On a comma list it carries each ETF's own position, so every ETF continues from its own last holding; a finished one returns an empty `holdings`.
tickerYesETF symbol, or a comma-separated list of up to 50 for a response keyed by symbol. Case-insensitive. Equities are bare symbols (`NVDA`); every other class carries a prefix: rates (`R:SOFR`), crypto (`X:BTCUSD`), fx (`X:EURUSD`). Bare `BTC`/`ETH` are US-listed ETFs, not spot crypto. See Tickers.

Output Schema

NameRequiredDescriptionDefault
dataYesThe ETF's holdings (on the list form, an object keyed by symbol): `is_etf` (from the instrument type on its ticker record), `count` (holdings in this page), `total` (the ETF's full holding count, on every page), `truncated` (`true` when more holdings follow this page, until 2027-01-12; from then `next_cursor` alone says so), `next_cursor` (this ETF alone), `holdings` (constituents, heaviest first, each `holding_ticker` and `weight`, a fraction: `0.0776` is 7.76%) and `sectors` (sector weights, heaviest first, in the vendor's ETF-profile vocabulary; always complete, `limit` is about `holdings`).
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
countNoWith a comma list: the symbols in `data`, that is, how many of the ETFs asked for were found. Until 2027-01-12 one ETF's read also carries it, as the holdings in this page (the same as `data.count`).
queryYesYour request echoed, each param with its effective value: `ticker` (a list even for one ETF) and `limit`.
not_foundNoWith a comma list only: the requested symbols we do not track, in request order; an empty array when every symbol was found; every symbol when none was (still a 200).
_advisoriesNoPresent only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).
next_cursorYesOpaque token for the next page; `null` once every ETF's holdings are complete. Pass it back as `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses result ordering, response shape (`data.holdings`, `data.sectors`), and two distinct edge cases distinguished via `data.is_etf` (non-ETF vs. real ETF with un-ingested holdings). It does not address auth/plan gating or rate limits, and pagination behavior is left entirely to the schema.

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?

Front-loads what is returned and in what order, then edge cases, then alternatives — good information ordering with no filler. Slightly dense with backticked field names, but every clause carries operational meaning.

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?

An output schema exists, yet the description still adds the interpretive layer that matters (is_etf semantics, empty-holdings meaning, ordering) rather than merely restating fields. Combined with the sibling routing note, an agent has everything needed to call this correctly and interpret the result.

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% and the parameter docs are unusually detailed (limit caps, clamping, cursor round-trip rules), so the schema does the heavy lifting. The description only restates the comma-list-of-50 bound already in the `ticker` parameter, adding no new parameter meaning. Baseline 3 applies.

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?

States a specific verb and resource ("Returns an ETF's constituents and their weights... and its sector weights") plus scope (one ETF or a comma list of up to 50) and ordering (heaviest first). An agent can immediately tell this apart from general quote/history siblings.

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 routes the agent away from this tool for the inverse question, naming both the alternative (`etf_holders` signal on tickerbot_get_ticker) and a scan fallback (`'SMH' = ANY(etf_holders)`). It also tells the agent what to expect when the ticker is not an ETF, which functions as a when-not condition.

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