Skip to main content
Glama
Unofficial Yahoo Finance MCP Server

Unofficial Yahoo Finance MCP Server

Fund profile

get_fund_data
Read-only

Fetch fund or ETF profile data for a Yahoo symbol, including overview, expense ratio, turnover, assets, returns, asset and sector weightings, and top holdings. Supports fund/ETF symbols only.

Instructions

Get fund/ETF profile data for a Yahoo symbol.

Returns the fund overview, key figures, asset-class and sector weightings, and the top holdings. The key figures are the expense ratio (with the category average), holdings turnover, total assets, and the returns year to date and averaged over three and five years. Ratios and returns are fractions, 0.0007 for 0.07%, and a figure Yahoo lacks is left out, which for European ETFs is often the returns and the size. Fund/ETF-only, raises for stocks and crypto, which have no fund data.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_fund_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of top holdings to return.
symbolYesA Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.8.6
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedInput schema / title
      Removed value: -"get_fund_dataArguments"
    • removedOutput schema / title
      Removed value: -"get_fund_dataDictOutput"
  2. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / symbol / maxLength
      Added value: +32
  3. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / symbol / description
      Previous value: -"A native Yahoo Finance ticker symbol, e.g. 'AAPL', 'MSFT', 'SAP.DE', or 'BMW.DE'. This is NOT an ISIN, a WKN, or a company name, and must NOT be built by appending an exchange suffix to an ISIN (e.g. 'US0378331005.DE' is invalid). If you only have a name or ISIN, call the 'search' tool first and pass the 'symbol' value it returns."New value: +"A Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first."
  4. First observedv0.2.2

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations by disclosing failure behavior (raises for stocks and crypto), unit conventions ('Ratios and returns are fractions, 0.0007 for 0.07%'), and a real-world data gap ('a figure Yahoo lacks is left out, which for European ETFs is often the returns and the size'). Those three facts materially change how an agent interprets results and handles partial data.

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-loaded with purpose and return contents, then closes with the constraint. The key-figures sentence is long but every clause names a distinct field, so it earns its length; only minor tightening is possible.

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, so return structure need not be restated; the description instead supplies the interpretive layer (fraction units, omitted figures, error on non-fund symbols) that the schema cannot. For a two-parameter read-only lookup, 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 coverage is 100%, with the schema already documenting both the symbol formats (ticker/ISIN) and the holdings limit. The description's mention of 'top holdings' loosely ties to the limit parameter but adds no syntax or behavioral detail beyond the schema, so the baseline of 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 ('Get fund/ETF profile data for a Yahoo symbol') and then enumerates the exact content returned: overview, key figures, asset-class and sector weightings, top holdings. The closing sentence 'Fund/ETF-only, raises for stocks and crypto' separates it cleanly from quote/company-info siblings that cover equities generally.

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?

Gives an explicit when-not condition ('raises for stocks and crypto, which have no fund data'), which is the key routing signal an agent needs. It stops short of naming the alternative tool for stocks (e.g. get_company_info or get_quote), so the agent must infer the fallback from sibling names.

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