Skip to main content
Glama
theodor90

form4api-mcp

by theodor90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_filings

Read-only

List Form 4 filings with optional ticker, CIK and date filters. Returns a paginated list of Form 4 filings, newest filed first. Filter by ticker, cik, and a from/to filed-date window.

Instructions

List Form 4 filings with optional ticker, CIK and date filters. Returns a paginated list of Form 4 filings, newest filed first. Filter by ticker, cik, and a from/to filed-date window. Each entry carries the accession number, company ticker/name, period of report, filed date, acceptedAt (the precise UTC SEC-acceptance instant, null if not captured), documentUrl (the public SEC document URL), amendment type (Original/Amendment), and the count of non-superseded transactions in that filing. Use this for a company's filing HISTORY; use GET /v1/filings/recent for a live newest-first feed (it has no page parameter), and GET /v1/transactions when you want the individual trades rather than the filings that contain them. limit is accepted as an alias for per_page. Not plan-gated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclusive end of the filed-date window, format YYYY-MM-DD.
cikNoCompany CIK (SEC identifier), e.g. "0000320193". Leading zeros optional.
fromNoInclusive start of the filed-date window, format YYYY-MM-DD.
pageNo1-based page number. Defaults to 1.
limitNoAlias for per_page. Accepted because every caller who hit this path before it existed sent `limit`.
tickerNoCompany ticker symbol, case-insensitive (e.g. "AAPL").
per_pageNoFilings per page. Defaults to 20, maximum 100. `limit` is accepted as an alias; if both are given, per_page wins.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.6

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses pagination, newest-filed-first ordering, the null semantics of acceptedAt, the alias behavior of limit, and the access state ('Not plan-gated'). These are exactly the behavioral traits an agent cannot get from the schema or annotations.

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 return shape, then routing guidance; each sentence carries weight. Slightly long because the filter list is effectively restated from the schema, but there is no 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?

With no output schema, the description fully enumerates the returned fields (accession number, ticker/name, period, filed date, acceptedAt, documentUrl, amendment type, transaction count) and notes pagination and ordering, so an agent knows both how to call it and what it gets back.

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 all seven params are already documented in the schema (including the limit/per_page alias and the 'per_page wins' rule). The description restates the ticker/cik/from-to filters but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 (List) and resource (Form 4 filings) with its filter dimensions, and explicitly distinguishes itself from sibling tools get_recent_filings and get_transactions by naming the alternative endpoints. An agent can identify the tool's role without opening any schema.

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?

Explicitly states 'Use this for a company's filing HISTORY', names the two alternative tools (recent live feed with no page param; transactions for individual trades) and the conditions that select each. Nothing is left to inference.

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

Deploy Server

Other Tools