Skip to main content
Glama

Fund Profile and Top Holdings

GetFundProfile
Read-only

Get a registered fund's profile and largest stored holdings from its latest SEC Form NPORT-P report. Accepts a profile ID, SEC series ID, stored ticker, or verified alias from SearchFunds. Returns registrant, series, assets, reported and stored holding counts, and the largest stored positions. Some multi-series trusts store only tracked-stock positions; reported counts and asset totals still describe the full filing. A row the report marks as securities-lending cash collateral is labelled in its category, and one line totals those rows. Use GetFundsHoldingStock for the inverse lookup.

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": {
      "fund": "<fund>"
    },
    "name": "GetFundProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundYesFund profile id, SEC series id, stored series ticker, or verified share-class alias from SearchFunds (e.g., 'ishares-russell-2000-etf-s000004344', 'S000004344', 'IWM', or 'VOO').
offsetNoNumber of ranked holdings to skip before returning rows (default: 0)
maxResultsNoMaximum number of holdings to return, largest first (default: 20, max: 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Number of ranked holdings to skip before returning rows (default: 0)",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / fund / description
      Previous value: -"Fund profile id from SearchFunds (e.g., 'ishares-russell-2000-etf-s000004344') or a fund's own ticker (e.g., 'IWM'). Share-class tickers of multi-class mutual funds (e.g. VOO, VFIAX) do not resolve — find the fund by name via SearchFunds."New value: +"Fund profile id, SEC series id, stored series ticker, or verified share-class alias from SearchFunds (e.g., 'ishares-russell-2000-etf-s000004344', 'S000004344', 'IWM', or 'VOO')."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare a read-only, closed-world, non-destructive operation, and the description adds real behavior beyond that: the data comes from the latest NPORT-P, some multi-series trusts store only tracked-stock positions, and reported counts/asset totals still describe the full filing. It also explains how securities-lending cash collateral rows are labelled and totalled. It stops short of discussing latency, pagination limits, or staleness of the stored 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?

The description is front-loaded with purpose and source, then caveats, then the alternative tool. It is a bit dense — six sentences where three might serve — but each sentence carries substantive information and none is filler.

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?

There is no output schema, so the description carries the return-value burden, and it does: registrant, series, assets, reported and stored holding counts, and the largest stored positions. The multi-series/store-only caveat and the collateral-row labelling rule cover the non-obvious edge cases an agent would otherwise be surprised by.

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%, so the schema already documents all three parameters including offset and maxResults defaults. The description restates the accepted identifier forms (profile id, series id, ticker, alias) but adds no format or syntax detail beyond the schema, so 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?

The opening sentence names a specific verb, resource, and data source: 'Get a registered fund's profile and largest stored holdings from its latest SEC Form NPORT-P report.' That lets an agent distinguish it from profile tools that use other filings, and the closing sentence explicitly routes the inverse case to GetFundsHoldingStock.

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?

The definition specifies which identifiers are accepted and points to GetFundsHoldingStock for the inverse lookup ('which funds hold a stock'). It does not contrast this tool with adjacent siblings such as GetEtfProfile or the Canadian/European fund holdings tools, so the routing guidance is clear but not exhaustive.

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.