Skip to main content
Glama

One fund's holdings (N-PORT)

fund_holdings
Read-onlyIdempotent

Return one fund's Form N-PORT portfolio: give a series id (S000002277) or a fund name, which is searched first. Positions are largest first with value in USD, balance, percent of net assets and the company when the CUSIP maps to one; data.periods lists other report months. Use it when asked what a fund holds.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fund": "Vanguard 500 Index",
      "limit": 10
    },
    "name": "fund_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundYesSeries id S000... or a fund name such as "Vanguard 500 Index".
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 25, at most 1000).
cursorNoOpaque cursor from a previous page (data.next_cursor).
periodNoReport month end; default the newest (YYYY-MM-DD).

Output Schema

NameRequiredDescriptionDefault
dataNo{ fund, period, periods, items: [holdings], next_cursor, note }
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: name-to-series resolution order, largest-first sorting, USD valuation and that data.periods carries other report months. It stops short of describing pagination/cursor behavior or coverage limits, so it is additive but not rich.

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 purpose and the input rule are front-loaded, and the output-field sentence is dense but earns its place by telling the agent what a position record contains. Slight compression into one block costs a little scannability.

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

Completeness4/5

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

With a 100% documented schema, an output schema and full annotations, the description only needs to supply purpose, call trigger and lookup behavior — all present. Nothing an agent needs before calling is missing, though pagination expectations are only implied.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the fund parameter's dual accepted form and — more importantly — that a fund name is resolved by search first. The as_of and period semantics are left entirely to the schema, which already documents them well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'Return one fund's Form N-PORT portfolio,' and the closing line 'Use it when asked what a fund holds' implicitly separates it from fund_nav (price) and fund_holders (ownership). It never names a sibling outright, so the differentiation is inferential rather than explicit.

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?

Provides a clear triggering question ('when asked what a fund holds'), which is enough context for an agent to prefer this over NAV or holders tools. It offers no when-not conditions and no named alternatives, leaving exclusion cases to inference.

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.

Resources