insidergraph

Recent filings firehose

list_recent_filings

Read-onlyIdempotent

The firehose: recently ingested filings across ALL feeds (Forms 3/4/5, 8-K, 144, Schedules 13D/13G) with acceptance timestamps and SEC filing links, newest first. Use to see what just came in.

Input Schema

TableJSON Schema

Name	Required	Description
`feeds`	No	Feeds to include. Empty = all.
`limit`	No	Max rows per page, default 50, cap 200.
`since`	No	Earliest acceptance time, RFC3339 or YYYY-MM-DD.
`cursor`	No	Opaque pagination token from the previous response's page.next_cursor; pass it back verbatim to fetch the next page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 4, 2026
- addedInput schema / properties / feeds / default
```
Added value: +[
+  "ownership",
+  "events",
+  "intents",
+  "stakes"
+]
```
Changed3 schema fields changedSep 2, 2026
- addedInput schema / $schema
```
Added value: +"https://json-schema.org/draft/2020-12/schema"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / limit / default
```
Added value: +50
```
First observedJul 5, 2026

TDQS

A4/5.0

Behavior3/5

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

With readOnlyHint and idempotentHint already present, the description adds ordering ('newest first'), content ('acceptance timestamps and SEC filing links'), and recency semantics ('recently ingested'). It does not discuss pagination or response shape in depth, but the schema already documents cursor-based pagination.

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 tight sentences: the core scope, content, and ordering are front-loaded, and the usage hint is one short clause. There is no redundancy or filler.

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?

For a read-only listing with fully documented optional parameters, the description provides sufficient return expectations by mentioning timestamps, links, and newest-first ordering. No output schema exists, so this description-level return info is valuable; pagination mechanics are handled by the cursor parameter schema.

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 explains feeds, limit, since, and cursor with defaults and format hints. The description adds no parameter semantics, but the baseline of 3 is appropriate when the schema carries full parameter documentation.

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 it lists recently ingested filings across all feeds with acceptance timestamps and SEC filing links, newest first. The verb 'list' and resource are explicit, and the firehose framing plus enumeration of form types separates it from type-specific siblings like get_insider_trades or get_material_events.

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?

The closing sentence 'Use to see what just came in' gives clear context: this is for recency monitoring across all feeds. It does not explicitly name alternatives or exclusions, but the 'ALL feeds' scope implies more targeted tools exist for specific feeds or filing types.

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

All insidergraph 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.

Resources

Need Help?