Skip to main content
Glama
brechanbech

SEC EDGAR MCP

by brechanbech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

Institutional Holdings (13F)

sec_institutional_holdings
Read-only

Retrieve an institutional manager's quarterly Form 13F holdings to see US-listed equity positions, values, portfolio percentages, and voting authority; filter by issuer or CUSIP.

Instructions

What an institutional manager holds: its quarterly Form 13F holdings report, read from the filing. Managers with $100 million or more in US-listed equities file one within 45 days of each quarter end. Pass the manager's CIK (find it with sec_lookup_cik's 'name', e.g. 'Bridgewater Associates'), or a ticker for a listed manager such as Berkshire Hathaway. Returns the latest report by default, or the one for 'report_period'; positions are aggregated by CUSIP, class and put/call across the table's rows and sorted by value, largest first, each with issuer, class, CUSIP, value in dollars, percent of the portfolio, shares (or principal), voting authority and investment discretion. 'query' narrows to an issuer by part of its name or by CUSIP: one call answers 'does Berkshire hold Apple'. Issuers are named as filed ('APPLE INC') and the table has no tickers, because CUSIP identifiers are licensed. This answers what one manager holds, not who holds a stock: for holders above 5% use sec_beneficial_ownership. 13F covers long positions in US-listed equities, options and some convertibles only, not shorts, cash or foreign shares, and may omit positions under confidential treatment. Amendments for the period are listed, not merged. Pages of 25 by default, at most 100; pass 'next_offset' back as 'offset'.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of positions to return, largest value first (default 25, max 100)
queryNoOptional: only positions whose issuer name contains this text, e.g. 'apple', or with this CUSIP. Issuers are named as filed ('APPLE INC').
offsetNoNumber of positions to skip, for paging (default 0). Pass the previous response's 'next_offset'.
tickerYesThe manager: its CIK (find it with sec_lookup_cik's 'name', e.g. 'Bridgewater Associates'), or a ticker for a listed one such as BRK-B.
report_periodNoOptional quarter end, YYYY-MM-DD, e.g. '2026-06-30'. Default: the latest report. The response lists the periods available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld, and the description adds substantial behavior well beyond them: aggregation by CUSIP/class/put-call, sort order by value descending, confidential-treatment omissions, amendments listed rather than merged, licensed CUSIPs meaning no tickers, and default-25/max-100 paging with next_offset.

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?

Front-loaded with the identity of the resource and then flows into inputs, return shape, and caveats in a logical order. It is a single very dense paragraph, though; splitting the coverage limitations and paging rules into separate sentences would help scanning without losing content.

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?

Covers everything an agent needs for a five-parameter, no-output-schema read tool: accepted identifier forms, default and paged return size, what each returned field contains, and the coverage caveats (long-only, no shorts/cash/foreign, confidential treatment, unmerged amendments).

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 already 100%, but the description still adds real meaning: 'ticker' accepts either a CIK or a listed manager's ticker (BRK-B), 'report_period' defaults to latest, 'query' matches issuer name fragment or CUSIP, and 'next_offset' feeds back into 'offset'.

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?

Opens with a specific verb+resource ("What an institutional manager holds: its quarterly Form 13F holdings report, read from the filing") and explicitly carves itself away from siblings, naming sec_beneficial_ownership for the inverse question and sec_lookup_cik for resolving the manager.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use sec_beneficial_ownership for holders above 5%, use sec_lookup_cik's 'name' to find a CIK, and use the 'query' parameter to answer "does Berkshire hold Apple". It also states what the tool is not for (who holds a stock, shorts, cash, foreign shares).

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

Deploy Server

Other Tools