Skip to main content
Glama
sec-edgar-fda-b2b-mcp

sec-edgar-fda-b2b-mcp

get_sec_13f_hedge_fund_holdings

Read-onlyIdempotent

Fetch quarterly SEC EDGAR Form 13F hedge fund holdings to inspect institutional equity positions, share counts, values, CUSIPs, and report dates. Returns JSON for specified institutions.

Instructions

Fetch quarterly US SEC EDGAR Form 13F institutional hedge fund portfolio holdings.

Use this tool to inspect major whale equity positions and share counts reported to the SEC.
Returns a JSON array of up to 25 holdings containing institution, issuerName, cusip,
valueUsd, shares, and reportDate. Requires the APIFY_TOKEN environment variable.

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": {
      "institutions": "<institutions>"
    },
    "name": "get_sec_13f_hedge_fund_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
institutionsYesList of institutional investment manager names to query (e.g., ['Berkshire Hathaway', 'Citadel Advisors']).
max_holdingsNoMaximum number of top portfolio positions to return per institution (1-100).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / institutions / description
      Added value: +"List of institutional investment manager names to query (e.g., ['Berkshire Hathaway', 'Citadel Advisors'])."
    • addedInput schema / properties / max_holdings / description
      Added value: +"Maximum number of top portfolio positions to return per institution (1-100)."
    • addedInput schema / properties / max_holdings / maximum
      Added value: +100
    • addedInput schema / properties / max_holdings / minimum
      Added value: +1
  2. First observedv0.1.0

TDQS

A3.9/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 open-world behavior, so the bar is lower. The description adds real value beyond them: the required APIFY_TOKEN environment variable and the returned array shape. Minor blemish: it says 'up to 25 holdings' when max_holdings permits 1-100, which could mislead an agent about result size.

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?

Three short, front-loaded statements: purpose, usage, then return/auth details. Nothing is padded, though the 'major whale' phrasing is informal and the fixed '25' slightly conflates the default with the actual maximum.

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 an output schema present, the description needn't explain return fields in depth, yet it still names them; annotations cover the safety profile; and the auth requirement is disclosed. Complete for a two-parameter read tool, with only the 25-vs-100 sizing detail left ambiguous.

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 description coverage is 100%, so both parameters (institutions list and max_holdings with its 1-100 bounds) are already fully documented. The description adds no new meaning about parameter syntax or behavior, so the baseline of 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 description opens with a specific verb and fully qualified resource: fetching quarterly US SEC EDGAR Form 13F institutional holdings. The domain (13F portfolio holdings) is distinct enough from siblings like get_sec_form4_insider_trades that an agent can disambiguate without opening the schema.

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 states a use case ('inspect major whale equity positions and share counts reported to the SEC'), which implies when to reach for it. However, it offers no exclusions and no comparison to the closely related Form 4 insider-trades tool, so an agent must infer the boundary itself.

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