Skip to main content
Glama

TickerInside ETF Holdings

by com.tickerinside
OverviewDiscussionsAdmin

ETFs that hold a stock

find_etfs_holding_stock
Read-onlyIdempotent

Use this when the user asks which ETFs hold a stock, which ETF holds the most of it, how many ETFs hold it, or whether it is in VOO, SPY, IVV, QQQ, VTI or SCHD. Returns the covered US ETFs that hold it, largest weight first, each with its weight, rank, dollars, holdings date and source, plus the count, how many hold it as their largest position, the ETFs and issuers with the most dollars in it, and one sentence to quote. The list keeps the heaviest holders; whether the six ETFs above hold it is in every answer for a stock with its own file, unless compact is true. ETFs holding it through swaps, futures or options are listed apart, as notional exposure. A private company's name in place of a ticker (ANTHROPIC, OPENAI) gives the US funds holding it, each stake and value per share from its SEC filing. Not for one stock's weight in another ETF (compare_stocks) or the share ETFs own (get_etf_ownership).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoHow many ETFs to return, sorted by the stock's weight in each ETF, largest first, from 1 to 200; 50 when left out.
tickerYesThe stock's ticker, not the company name, for example NVDA for Nvidia. A line listed outside the US carries its market after a dot, for example 7203.JP (Toyota in Tokyo), SAN.FR (Sanofi in Paris) or 005930.KR (Samsung Electronics); an earlier key without the market, such as 7203, is read as the key it became. A key ending in .PFD is not a market: it is the issuer's preferred shares, a US line apart from the common stock (JPM.PFD, held by preferred stock ETFs).
compactNotrue for an answer about half the length. It keeps the counts, rank_summary (how many ETFs hold the stock as their largest or a top 10 position), name_collision (ETFs whose name contains the company's name) and the sentence to quote. It leaves out top_by_value (the ETFs holding the most dollars of it), membership (whether VOO, SPY, IVV, QQQ, VTI and SCHD hold it, and its weight in the three largest sector or industry ETFs that hold it), by_issuer (the issuers holding the most dollars), fee_per_1000 (the yearly cost, in the cheapest ETFs, of each $1,000 of the stock held through them) and each ETF's rank, positions and value.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
heldNo
nameNo
answerNoOne sentence to quote.
sourceNo
tickerYes
held_byNoLargest weight first.
membershipNo
rank_summaryNo
funds_holdingYes
funds_by_sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / compact / description
      Previous value: -"true for an answer about half the length. It keeps the counts, rank_summary (how many funds hold the stock as their largest or a top 10 position), name_collision (funds whose name contains the company's name) and the sentence to quote. It leaves out top_by_value (the funds holding the most dollars of it), membership (whether VOO, SPY, IVV, QQQ, VTI and SCHD hold it, and its weight in the three largest sector or industry funds that hold it), by_issuer (the issuers holding the most dollars), fee_per_1000 (the yearly cost, in the cheapest funds, of each $1,000 of the stock held through them) and each fund's rank, positions and value."New value: +"true for an answer about half the length. It keeps the counts, rank_summary (how many ETFs hold the stock as their largest or a top 10 position), name_collision (ETFs whose name contains the company's name) and the sentence to quote. It leaves out top_by_value (the ETFs holding the most dollars of it), membership (whether VOO, SPY, IVV, QQQ, VTI and SCHD hold it, and its weight in the three largest sector or industry ETFs that hold it), by_issuer (the issuers holding the most dollars), fee_per_1000 (the yearly cost, in the cheapest ETFs, of each $1,000 of the stock held through them) and each ETF's rank, positions and value."
    • changedInput schema / properties / ticker / description
      Previous value: -"The stock's ticker, not the company name, for example NVDA for Nvidia. A line listed outside the US carries its market after a dot, for example 7203.JP (Toyota in Tokyo), SAN.FR (Sanofi in Paris) or 005930.KR (Samsung Electronics); an earlier key without the market, such as 7203, is read as the key it became. A key ending in .PFD is not a market: it is the issuer's preferred shares, a US line apart from the common stock (JPM.PFD, held by preferred stock funds)."New value: +"The stock's ticker, not the company name, for example NVDA for Nvidia. A line listed outside the US carries its market after a dot, for example 7203.JP (Toyota in Tokyo), SAN.FR (Sanofi in Paris) or 005930.KR (Samsung Electronics); an earlier key without the market, such as 7203, is read as the key it became. A key ending in .PFD is not a market: it is the issuer's preferred shares, a US line apart from the common stock (JPM.PFD, held by preferred stock ETFs)."
    • changedInput schema / properties / top / description
      Previous value: -"How many funds to return, sorted by the stock's weight in each fund, largest first, from 1 to 200; 50 when left out."New value: +"How many ETFs to return, sorted by the stock's weight in each ETF, largest first, from 1 to 200; 50 when left out."
    • changedOutput schema / properties / held_by / items / properties / weight_pct / description
      Previous value: -"The stock's weight in the fund."New value: +"The stock's weight in the ETF."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare read-only, idempotent, non-destructive, closed-world behavior, and the description still adds substantial operational context beyond them: results are ordered largest-weight-first, the heaviest holders dominate the list, membership answers persist unless compact=true, swap/futures/options exposure is reported separately as notional, and private-company names map to SEC filings. This is a rich behavioral profile a caller cannot get from annotations alone.

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?

Usage triggers and the anti-pattern routing are front-loaded, and each sentence conveys distinct information. It is still one very long, dense paragraph that repeats some return-field detail already implied by the output schema and the compact parameter description.

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?

For a single-ticker lookup with rich annotations and an output schema, the description covers triggers, alternatives, ordering, edge cases (non-US tickers, preferred shares, private companies, notional exposure) and the compact trade-off. Nothing an agent needs to call it correctly is missing.

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 three parameter descriptions are already detailed, including the default for top and the full content delta for compact. The description restates the ticker formats and compact effects rather than adding new semantics, beyond noting that the six-ETF membership check appears in every answer unless compact is true. Baseline 3 is appropriate when the schema carries the parameter burden.

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 names a specific verb+resource ('ETFs that hold a stock') and enumerates the exact question shapes it answers, including which ETF holds the most, how many hold it, and index-membership checks. It explicitly separates itself from compare_stocks and get_etf_ownership, so an agent can route without opening a schema.

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?

It gives concrete when-to-use triggers (the user's question phrasings, the six specific ETFs) and explicit when-not-to-use cases with named alternatives ('Not for one stock's weight in another ETF (compare_stocks) or the share ETFs own (get_etf_ownership)'). Nothing is left to inference.

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

All TickerInside ETF Holdings toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources