Skip to main content
Glama

Returns the latest Form 13F-HR holdings

sec_13f
Read-only

Returns the latest Form 13F-HR holdings for an institutional investor by CIK or name search. Each holding: issuer, class, CUSIP, value in USD, shares, put/call flag, largest first. Capped at 500 rows. Also returns the total value from the cover page, filing date and reporting period. Source: SEC EDGAR (public domain). EDGAR requests ≤10/s. Related tools on this server, for a different need: sec_insiders when you need to list the latest Form 4 insider trades of a US company; sec_events when you need to list a US company's latest 8-K filings and their items. Price: $0.004 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "sec_13f"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoFiler CIK number (10-digit, with or without leading zeros)
nameNoFiler name to search EDGAR (used when cik is not given; picks the top match)
limitNoMax holdings rows to return (1–500, default 100)

Output Schema

NameRequiredDescriptionDefault
cikNo
noteNo
sourceNo
edgarUrlNo
holdingsNo
checkedAtNo
filerNameNo
truncatedNo
disclaimerNo
filingDateNo
holdingsCountNo
totalValueUsdNo
entriesInFilingNo
reportingPeriodNo
totalValueSourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / entriesInFiling
      Added value: +{}
    • addedOutput schema / properties / note
      Added value: +{}
    • addedOutput schema / properties / totalValueSource
      Added value: +{}
    • removedOutput schema / properties / totalValueThousands
      Removed value: -{}
    • addedOutput schema / properties / totalValueUsd
      Added value: +{}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the 500-row cap, the 'largest first' ordering, the EDGAR rate limit (≤10 requests/s), the public-domain source, and the billing model ($0.004 per successful call, failures uncharged). The cost and rate-limit details are operationally relevant facts an agent cannot get from annotations or schema.

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 shape, then limits, source, rate limit, alternatives, and price — a sensible ordering with no filler. It is dense and the pricing/related-tools sentences are long, but each carries distinct decision-relevant information.

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?

With an output schema present and full schema coverage, the description need not restate return structure, yet it still summarizes the holdings fields and adds the cover-page total, filing date, and reporting period. Combined with the cap, ordering, rate limit, and cost, an agent has everything needed to call this correctly.

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 the parameters are already documented, and the description's parameter-relevant content ('by CIK or name search', 'Capped at 500 rows') largely restates the schema's 'used when cik is not given' and '1–500, default 100'. It adds no format, precedence, or syntax detail beyond what the schema supplies.

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?

States a specific verb and resource ('Returns the latest Form 13F-HR holdings') plus the two lookup keys (CIK or name search) and the subject (an institutional investor). It then enumerates the returned fields, which lets an agent confirm this is the holdings tool rather than a filing-list or insider tool.

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

Usage Guidelines4/5

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

Explicitly routes to two alternatives with their conditions ('sec_insiders when you need to list the latest Form 4 insider trades...; sec_events when you need to list a US company's latest 8-K filings'), which is exactly the kind of disambiguation needed. It stops short of stating when NOT to use this tool (e.g., preference rules vs. the general sec_filings sibling), so it is clear context without full exclusions.

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