Skip to main content
Glama
edgar13f-mcp

edgar13f-mcp

by Serios16

list_13f_filings

List a manager's SEC Form 13F filings filed by a chosen as_of date, optionally filtered to one report period, to reconstruct what was publicly known.

Instructions

Every Form 13F submission (13F-HR, 13F-HR/A, 13F-NT, 13F-NT/A) by the manager whose EDGAR filing date is on or before as_of (what was publicly filed by then). Pass period to list only the filings for one report period.

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>",
      "as_of": "<as_of>"
    },
    "name": "list_13f_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesSEC Central Index Key; leading zeros optional. Resolve a manager's name to its CIK with find_manager.
as_ofYesISO-8601 knowledge date: the answer uses only what was publicly filed on EDGAR by this date.
periodNoForm 13F report period: a calendar quarter-end date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it does disclose the important point-in-time semantics ('what was publicly filed by then') and that amendments and notices are included. It says nothing about result ordering, pagination, how amendments relate to originals, or what an empty result means, which are material gaps for a filing-list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the core enumeration and the as_of cutoff front-loaded before the optional period filter. Each clause carries information not already in the 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?

There is no output schema and no annotations, and the description adequately covers the temporal semantics and the form-type scope of the result. It falls short only on return shape details (ordering, pagination, amendment linkage) that an agent might want, but the core call behavior is unambiguous.

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 100%, so the baseline is 3, but the description adds real meaning: as_of is framed as a knowledge cutoff describing public availability, not a report date, and period is framed as a narrowing filter over the report period. That distinction is the main source of misuse risk and the description addresses it directly.

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?

The description names the specific resource (Form 13F submissions by a manager) and enumerates the exact form types returned (13F-HR, 13F-HR/A, 13F-NT, 13F-NT/A), which is concrete and verifiable. It does not explicitly differentiate itself from siblings such as get_holdings_as_of or diff_holdings, so the agent must infer the boundary from the resource type alone.

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 is implied rather than stated: the description implies you use this to see what filings existed as of a date, and that period narrows to one report period. It never names an alternative like get_holdings_as_of or diff_holdings, nor does it say when this tool is the wrong choice versus looking at holdings.

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