Skip to main content
Glama
theodor90

form4api-mcp

by theodor90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_schedule13_dg

Read-only

List Schedule 13D/13G >5% beneficial-ownership crossings (Business plan+). Returns every parsed >5% beneficial-ownership crossing event for a company — filer/reporting person, ownership percent, event date, form type (13D or 13G), and…

Instructions

List Schedule 13D/13G >5% beneficial-ownership crossings (Business plan+). Returns every parsed >5% beneficial-ownership crossing event for a company — filer/reporting person, ownership percent, event date, form type (13D or 13G), and amendment status — parsed from EDGAR's structured Schedule 13D/13G cover-page XML (mandatory since the SEC's 2023 rule, compliance date 2024-12-18). SC 13D indicates an "active" investor who may seek control or influence over the issuer and must file within five business days of crossing the threshold (shortened from 10 days by the SEC's 2023 rule amendments, effective 2024-02-05); SC 13G is a lighter, less frequent filing for "passive"/qualified investors (e.g. index funds), with its own accelerated deadlines effective 2024-09-30. A single accession can carry several rows when the filing is a joint filing (e.g. a fund, its general partner, and the individual who controls both) — each reporting person has its own ownership percent. Results exclude rows superseded by a later SC 13D/A or SC 13G/A amendment; the isAmendment field on a returned row indicates whether that row is itself an amendment, not whether it has since been superseded. Requires Business plan or higher (402 PLAN_REQUIRED on Free/Starter/Pro). limit is accepted as an alias for per_page. Query runs live against the database — no caching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number. Defaults to 1.
limitNoAlias for per_page.
tickerNoCompany ticker symbol, case-insensitive (e.g. "AAPL"). Omit to search across all companies.
per_pageNoRows per page. Defaults to 50, maximum 200. `limit` is accepted as an alias; if both are given, per_page wins.
form_typeNoFilter to one form type: "13D" (active investor, may seek control/influence) or "13G" (passive/qualified investor). Case-insensitive. Omit for both.
is_amendmentNoWhen true, only returns amendments (SC 13D/A or SC 13G/A rows). When false, only returns original filings. Omit for both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.7

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that superseded SC 13D/A and 13G/A rows are excluded, that isAmendment describes the row itself rather than supersession, that the query runs live with no caching, and that Free/Starter/Pro get a 402 PLAN_REQUIRED error. These are exactly the operational traits an agent needs that the readOnly/openWorld hints do not carry.

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

Conciseness3/5

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

Front-loaded correctly with the tool's scope in sentence one, but the middle is padded with regulatory lore (2023 rule compliance dates, 10-to-5-day deadline history, 2024-09-30 effective dates) that does not help selection or invocation. The load-bearing facts (superseded-row exclusion, isAmendment semantics, plan gate) have to be dug out of a dense block.

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 compensates by naming the returned fields and the joint-filing multi-row behavior. Combined with the plan requirement, live-query note, and alias handling, an agent has everything needed to call it correctly for a read-only listing 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 coverage is 100%, so the schema already documents every parameter including the limit/per_page alias and the 13D/13G meanings. The description largely restates that schema text (e.g. the limit alias) rather than adding new semantics, so the baseline of 3 holds.

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 opens with a specific verb+resource+scope ('List Schedule 13D/13G >5% beneficial-ownership crossings (Business plan+)') and enumerates the returned fields (filer, ownership percent, event date, form type, amendment status). The resource is narrow enough to separate it from generic siblings like list_filings or get_form144, though no sibling is explicitly named for contrast.

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 explains what 13D vs 13G mean and that results exclude superseded rows, letting an agent infer when this beats a generic filings list. It never says when to prefer this over list_filings/get_filing, nor any when-not condition beyond the plan gate.

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