Skip to main content
Glama

Latest 13F Filings

GetLatest13FFilings
Read-only

List the newest SEC 13F-HR filings loaded here, newest filing day first: filer, CIK, report quarter, SEC filing date, when the filing was loaded (UTC), original or amendment, tracked positions and tracked value. Opens with how many filings are loaded per recent filing day and when the newest of them was loaded, so you can tell whether a quarter's filings are in before reading a filer's holdings. Filter by reportDate (a quarter end) or filedSince. A filing appears only after it is filed with the SEC and loaded; a filer absent from the list has no newer 13F on file here.

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

Input Schema

NameRequiredDescriptionDefault
offsetNoNumber of filings to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the current offset.
filedSinceNoEarliest SEC filing date in YYYY-MM-DD format (omit for no lower bound)
maxResultsNoMaximum number of filings to return (default: 20, clamped to 1-500)
reportDateNoQuarter-end 13F report date in YYYY-MM-DD format to list only that quarter's filings (omit for every quarter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare a safe read, so the description adds genuine behavioral context instead of repeating it: newest-first ordering, ingestion latency ('a filing appears only after it is filed with the SEC and loaded'), and absence semantics ('a filer absent from the list has no newer 13F on file here'). These are exactly the caveats an agent needs to avoid misreading an empty result as 'no holdings'.

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 purpose, then returned fields, then ingestion caveats, then filters — a sensible order with no filler. The field enumeration is dense but earns its place given there is no output schema.

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 no output schema, the description carries the return shape and does so thoroughly, plus ordering and coverage caveats. Pagination behavior (offset/maxResults) is left entirely to the schema, which is a minor gap for a paged list tool.

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 schema already defines all four parameters including formats and clamping. The description only restates the two filters and adds the parenthetical that reportDate is a quarter end, which is marginal added meaning.

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 (list the newest SEC 13F-HR filings) and enumerates the returned fields and ordering. It never names a sibling alternative such as ListFilings, so it falls short of the full 5 by not differentiating itself from the broader filings 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?

Gives a concrete usage context: the per-day count header lets an agent confirm a quarter's filings are loaded before reading a filer's holdings. Filter guidance (reportDate for a quarter end, filedSince for a lower bound) is explicit, but no when-not-to-use or named alternative is offered.

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.