Skip to main content
Glama

beatandraise.com SEC Filings

Get 13F Holdings

get_holdings
Read-onlyIdempotent

Get parsed 13F-HR institutional holdings for a filer.

Returns individual stock positions with issuer name, CUSIP, FIGI, market value, share count, investment discretion, and voting authority, parsed from the 13F information table XML ("format": "xml"), as filed: one row per entry, values in the filer's unit (thousands of dollars for most filings before 2023, dollars since).

13F-HRs filed before SEC introduced the XML table (2013 Q2) carry their holdings as a plain-text table in the filing's own document. For those the result has "format": "text" and "text": that document as filed, paged by line (limit/offset count lines, total_lines says how many). Read the table from it; search_document on its filename finds one position. "period" in the result is the quarter the report covers; "filing_date" is about 45 days later. A "period_note" says when the filer has no 13F for the period asked for and an earlier one is returned (that quarter is not filed yet, or the filer stopped).

Each holding also carries issuer_cik, sic and sic_description (the SEC's SIC industry classification of the issuer, not GICS) when the CUSIP maps to a company with a SIC. In a typical quarter that is about 87% of the value held; funds, ETFs, options and unmapped CUSIPs have none. "with_sic" in the result says how many holdings on this page were classified, so say how much of a portfolio an industry breakdown covers. Use sic_url from get_company to see peers in an industry.

Args: cik: CIK of the 13F filer / institutional investor (e.g. "1535950") period: Report period (YYYY-MM-DD), e.g. 2026-06-30 for the second quarter: the 13F for that period, else the latest period before it. Default: the latest period. limit: Max holdings per page (1-5000, default 500) offset: Pagination offset

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": {
      "cik": "<cik>"
    },
    "name": "get_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYes
limitNo
offsetNo
periodNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that pre-2013 Q2 filings return a different 'format' ('text' vs 'xml') with line-based pagination where limit/offset count lines and total_lines reports the size, that values are in thousands before 2023 and dollars after, and that only ~87% of holdings carry SIC. These are exactly the quirks an agent would otherwise get wrong.

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-loads purpose, then return semantics, then edge cases, then args — a sensible order, and nearly every sentence carries real information. It runs long with a few accretions (the sic_url/get_company aside) that could be trimmed without loss.

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?

For a tool with several parsing quirks, the description covers format switching, unit scaling across eras, pagination semantics that differ by format, and SIC coverage — nothing an agent needs to interpret results correctly is missing, and the output schema handles field structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the full load — and it does: cik is given an example, period is defined as a YYYY-MM-DD report period with an example, default-latest behavior, and a fallback to the most recent prior period, and limit/offset are described with ranges and defaults plus the crucial note that they page lines for text-format filings.

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?

States a specific verb and resource ('Get parsed 13F-HR institutional holdings for a filer') and enumerates the returned fields, which is far more precise than a generic holders tool. However, it never names or contrasts with the sibling get_institutional_holders, so an agent must infer which of the two to call.

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 context is implied through the period fallback rule ('the 13F for that period, else the latest period before it') and the period_note behavior, which tells the agent what happens when a quarter isn't filed. There is no explicit when-to-use/when-not guidance and no routing against get_institutional_holders or get_company.

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