Skip to main content
Glama
Sign In

InsiderRadar

by nl.insiderradar
OverviewDiscussionsAdmin

Holdings of followed fund managers (SEC Form 13F)

get_fund_holdings
Read-onlyIdempotent

The quarterly 13F holdings of the fund managers InsiderRadar follows (e.g. Berkshire Hathaway, Baupost): give fund for one manager's positions in a quarter, or issuer for which followed managers held a company. Each position has the shares and value in USD this quarter and the previous one, whether it is new, increased, decreased, sold out or unchanged, and its share of everything the fund reported. Default quarter: each fund's latest report. Holdings at quarter end, filed up to 45 days later; no prices paid, no short positions, no cash.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fund_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundNoPart of the fund's name or its figurehead (Berkshire, Buffett, Baupost), or its SEC CIK.
limitNoHow many positions to return, largest value first. Default 25.
issuerNoPart of the company name as the fund reports it, e.g. Apple.
statusNoOnly new, increased, decreased, exited (sold out) or unchanged positions. Default all.
quarterNoThe quarter end, e.g. 2026-06-30. Default: each fund's latest report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Although annotations already cover read-only, idempotent, closed-world, and non-destructive behavior, the description adds important domain context: quarter-end holdings filed up to 45 days later, defaulting to each fund's latest report, and exclusions such as no prices paid, no short positions, and no cash. It also describes the comparative fields returned for each position.

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 dense but front-loads the resource and query modes, and every sentence contributes useful information about returns, defaults, or limitations. The long first sentence is somewhat hard to parse, but overall the structure remains efficient.

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?

For a five-parameter read-only holdings tool with no output schema, the description supplies the main return fields, defaults, filing lag, and data exclusions. It could be more complete about how results are organized for issuer searches and how `limit` applies across multiple managers, but it is otherwise sufficient.

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, but the description adds meaningful interpretation: `fund` targets one manager's positions in a quarter, while `issuer` targets companies held by followed managers. It also reinforces the default quarter behavior, though most other parameter details remain in the schema.

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?

The description clearly identifies the resource as quarterly SEC Form 13F holdings for followed fund managers and explains the fund vs. issuer query modes. It is specific, but it does not explicitly differentiate this tool from sibling tools such as insider or politician activity searches.

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?

It gives implied usage by explaining that a fund query returns one manager's positions while an issuer query returns companies held by followed managers. However, it does not state explicit when-to-use or when-not-to-use guidance, nor does it name alternatives among the sibling tools.

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

All InsiderRadar toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources