Skip to main content
Glama

ETF Profile and Performance

GetEtfProfile
Read-only

Get ETF settled performance, SEC assets, allocation and top holdings. For this exact ETF ticker, use GetStockPrices or GetLatestClosingPrices for prices, GetLiveQuote for entitled intraday quotes, GetOptionExpirations/GetOptionChain/GetOptionContract/GetOptionContractHistory for options, GetShortInterest for reported short interest and days to cover, GetShortVolume/GetOffExchangeVolume/GetFailsToDeliver for trading and settlement data, GetTopHolders/GetInstitutionalOwnershipHistory/GetTopInstitutionalBuyersSellers for 13F institutional exposure, GetFundsHoldingStock for funds owning the ETF, GetDividendHistory for its own declared distributions, and GetCongressionalTrades for congressional trades. These are shared stock-and-ETF tools; GetEtfHoldings instead returns investments inside the ETF. ListFilings/SearchDocuments select the SEC registrant and may include sibling funds, not just this ETF series. Issuer-trained short-interest forecasts and squeeze scores are not ETF analytics.

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": "GetEtfProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesExact exchange-traded ticker (for example SPY, VOO, or IVV), or MIC:TICKER for a fund listed on another exchange (for example XETR:SXR8).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Exact exchange-traded ticker (for example SPY, VOO, or IVV)."New value: +"Exact exchange-traded ticker (for example SPY, VOO, or IVV), or MIC:TICKER for a fund listed on another exchange (for example XETR:SXR8)."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so safety is covered; the description adds real value beyond them. "Settled performance" signals the data is end-of-day settled rather than intraday, and the ListFilings/SearchDocuments caveat warns that filings resolve to the SEC registrant and may include sibling funds rather than this ETF series. It stops short of describing response shape, freshness lag or entitlement requirements.

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

Conciseness2/5

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

The first sentence is well front-loaded, but the rest is one sprawling enumeration of fifteen-plus siblings, including irrelevant ones like GetOptionContractHistory and GetCongressionalTrades that no agent would confuse with an ETF profile. Most of that routing bulk costs tokens without changing tool selection.

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

Completeness3/5

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

For a single-parameter read tool with annotations covering safety and no output schema, the description covers what is returned, which sibling to use instead, and two caveats about data scope. It is adequate but the hedging is spent on exhaustive sibling routing rather than on what the profile response actually contains.

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% and the schema already documents the exact-ticker and MIC:TICKER forms with examples. The description only echoes the exact-match requirement ("For this exact ETF ticker") without adding format, validation or fuzzy-match behavior beyond the schema, so the 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?

"Get ETF settled performance, SEC assets, allocation and top holdings" names a specific verb plus four concrete resource types, and the description immediately contrasts itself with GetEtfHoldings ("investments inside the ETF"). An agent can distinguish this from the closest sibling 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 explicitly routes every adjacent need to a named alternative: prices to GetStockPrices/GetLatestClosingPrices, quotes to GetLiveQuote, options to GetOptionChain family, short data to GetShortInterest/GetShortVolume, ownership to GetTopHolders, distributions to GetDividendHistory. The when-not is stated too (GetEtfHoldings for constituents), with no inference required.

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.