Skip to main content
Glama

SN Data by Shikshan Nivesh

A fund's 13F holdings

get_fund_holdings
Read-onlyIdempotent

One fund's latest 13F: each holding with shares, value, weight in the fund, the change from the quarter before and whether it is new, added, trimmed, exited or held, plus the fund's value and positions each quarter. Largest holdings first.

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

Input Schema

NameRequiredDescriptionDefault
fundYesThe fund's CIK (like 1067983) or its slug from search_funds (like berkshire-hathaway-inc-1067983).
moveNoOnly holdings with this move in the latest quarter.
limitNoMost holdings to return, largest first. Default 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 behavior the annotations cannot: results are the latest 13F quarter, ordered largest-first, include a cross-quarter comparison and a per-quarter fund value/position series. It stops short of stating freshness/lag of 13F filings or what happens when a fund has no filing.

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?

Two sentences, front-loaded with the resource, and every clause carries content about what is returned. The middle clause ("the change from the quarter before and whether it is new, added, trimmed, exited or held") is dense and slightly redundant, but nothing is filler.

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 no output schema, the description correctly takes on the job of describing the return payload — per-holding fields plus a fund-level per-quarter series — which is what an agent needs to plan parsing. Remaining gaps are minor: no note on filing recency, truncation behavior when limit clips results, or empty-result handling.

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 the fund identifier formats, the move enum values and the limit default/bounds. The description adds only indirect meaning: it links the new/added/trimmed/exited/held vocabulary to "the change from the quarter before," which slightly clarifies the enum's semantics, but it does not explain what the move filter does or how limit interacts with the largest-first ordering.

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?

"One fund's latest 13F" states a specific resource and directionality (fund -> holdings), and the enumeration of returned fields (shares, value, weight, quarter-over-quarter change, move classification) makes the shape concrete. It implicitly separates itself from company-centric siblings like get_company_fund_holders by anchoring on a single fund, but it never names or contrasts an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer you call this when you have a fund CIK or slug and want its positions. There is no statement of when to prefer it over get_company_fund_holders, get_large_holders, or search_funds, and no prerequisites or exclusions are given.

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