Skip to main content
Glama
Sign In
Portfolio Analytics MCP

Portfolio Analytics MCP

by RugSec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_etf_holdings

Read-only

Retrieve an ETF's top holdings and each company's weight percentage from Yahoo, plus total fund coverage.

Instructions

Top holdings of an ETF with each company's % weight, from Yahoo.

Yahoo usually exposes only the top ~10 holdings; `total_pct_covered`
shows how much of the fund that is. For UCITS ETFs and portfolio-level
overlap, prefer get_etf_exposure / analyze_portfolio (justETF, by ISIN).

Args:
    ticker: Yahoo symbol of the fund, e.g. "QQQ", "IWDA.AS".

Returns:
    `holdings` (symbol, name, weight_pct) and `total_pct_covered`; or an
    error dict.

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

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds important behavioral context beyond them: the Yahoo source, the top ~10 holdings limitation, the meaning of total_pct_covered, and the return/error shape. This is materially useful for interpreting the tool's output limitations.

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

Conciseness5/5

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

The description is compact and front-loaded: it states the core purpose first, then the Yahoo limitation and alternatives, then Args and Returns. Every section earns its place, especially since there is no output schema and the parameter schema has no descriptions.

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 low-complexity, one-parameter, read-only tool with no output schema, the description covers the essential context: data source, result limitations, alternative tools, ticker format, and returned fields. Nothing critical is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the single ticker parameter, and it does: it specifies that ticker is a Yahoo symbol of the fund and supplies examples such as "QQQ" and "IWDA.AS". That is enough to prevent confusion with ISIN-based or other symbol formats.

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 and resource: fetch the top holdings of an ETF with each company's percentage weight from Yahoo. It also distinguishes itself from related tools by pointing to get_etf_exposure and analyze_portfolio for UCITS and portfolio overlap cases.

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 explicit routing guidance: use this tool for top holdings, but prefer get_etf_exposure or analyze_portfolio for UCITS ETFs and portfolio-level overlap. It also warns that Yahoo typically exposes only the top ~10 holdings, which helps the agent decide whether the result is sufficient.

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

Deploy Server

Other Tools