Sec Beneficial Ownership

Sec 13d Search

sec_13d_search

Read-onlyIdempotent

MARKET-WIDE search of Schedule 13D / 13G beneficial-ownership filings by FILING DATE — no ticker needed. AUTHORITATIVE for "which activist investors filed new 13Ds this month and which companies did they target", "who disclosed a 5%+ stake in anything last week", "new 13G filings since Monday". Returns, per filing: the SUBJECT company (the issuer targeted, with ticker and CIK), the FILERS (investors / reporting persons, with CIK), form, filing date, and whether it is an amendment. By default only NEW filings (amendments excluded; set include_amendments true to add 13D/A and 13G/A). For the first enrich structured filings (post-2024 XML rule, default 5, max 10) it also reads the filing itself and adds the reporting owners' percent of class and shares owned, the event date, and — for 13D — the Item 4 "Purpose of Transaction" text (the activist signal). Rows beyond enrich carry the index fields only; pass their accession to sec_13d_filing for the full parse. total_matches is the true count for the window, scanned how many were read (at most 300), and truncated says honestly when the window held more than was scanned — narrow the date range rather than assuming completeness. Default window: the last 30 days.

Input Schema

Name	Required	Description
`limit`	No	Max filings to return (1-100, default 25), newest first.
`enrich`	No	How many of the returned structured filings to read in full for percent of class and Item 4 purpose (0-10, default 5). Each is one SEC document fetch.
`end_date`	No	Last filing date, YYYY-MM-DD. Default: today.
`start_date`	No	First filing date, YYYY-MM-DD. Default: 30 days before end_date.
`form_family`	No	"13D" (default; active / activist stakes), "13G" (passive 5%+ holders) or "all".
`include_amendments`	No	Include 13D/A and 13G/A amendments. Default false (new filings only).

Output Schema

Name	Required	Description	Default
`note`	No
`source`	No
`results`	No
`scanned`	No
`returned`	No
`truncated`	No
`data_as_of`	No
`date_range`	No
`form_family`	No
`total_matches`	No
`include_amendments`	No
`matched_after_filter`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds important operational context: default exclusion of amendments, enrichment limits, row-level enrichment cutoff, the 300-row scan cap, and truthful total_matches/scanned/truncated reporting.

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?

The description is dense but front-loaded, leading with the market-wide scope and then covering defaults, enrichment, and truncation. Every sentence contributes operational guidance without filler.

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?

Given rich annotations, a full input schema, and an output schema, the description completes the picture with default behavior, enrichment semantics, scan limits, and truncation handling. Nothing an agent needs to invoke the tool correctly appears missing.

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 structured fields already document each parameter; the description adds useful meaning about the enrich cutoff and include_amendments default. It does not add much syntax beyond the schema, but it clarifies how key parameters affect returned data.

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: a market-wide search of Schedule 13D/13G beneficial-ownership filings by filing date, with no ticker required. It also distinguishes itself from sec_13d_filing by directing agents there for full filing parses.

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 use cases for market-wide questions, explains the default new-filings-only behavior, tells when to set include_amendments, and names the alternative sec_13d_filing for enriched or un-enriched rows. It also advises narrowing the date range when truncated rather than assuming completeness.

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

All Sec Beneficial Ownership tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.