Skip to main content
Glama

hedge-fund-holdings

Retrieve top stock holdings from any institution's latest SEC 13F filing, with positions ordered by market value.

Instructions

Returns top stock holdings from any institution's latest SEC 13F filing. Input: institution name (e.g. 'Renaissance Technologies', 'Bridgewater Associates'). Output: top 25 positions by market value with shares, value, and portfolio weight. No API key. SEC EDGAR source. $0.025 vs $25-50/mo Quiver Quant subscription.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
institutionNoInstitutional investor name as it appears in SEC filings (e.g. 'Renaissance Technologies', 'Berkshire Hathaway', 'Two Sigma').
limitNoMax number of top holdings to return (default: 25, max: 100).
include_optionsNoIf true, includes PUT and CALL option positions alongside equity holdings. Default: false (equity SH positions only).
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the data source (SEC EDGAR), output details, and cost comparison. However, it does not mention rate limits, data freshness, or error scenarios.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: first states purpose, second provides input/output details and cost context. Front-loaded and no wasted words.

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?

Given the tool's simplicity (3 parameters, no output schema), the description adequately covers input, output format, and data source. No gaps for an agent to misinterpret.

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 descriptions for all three parameters. The description adds institution name examples but does not significantly enhance understanding beyond the schema. Baseline 3 is appropriate.

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 description clearly states it returns top stock holdings from an institution's latest SEC 13F filing, specifying input (institution name) and output (top 25 positions with shares, value, weight). It is distinct from sibling tools like etf-holdings or insider-trades.

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?

The description does not explicitly state when to use this tool versus alternatives such as etf-holdings or sec-filing-intel. It mentions a cost comparison but lacks guidance on context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thebrierfox/the-stall'

If you have feedback or need assistance with the MCP directory API, please join our Discord server