Skip to main content
Glama

filingpulse

by io.filingpulse

Form 4 insider transactions

get_insider_trades
Read-only

List normalized SEC Form 4 insider-transaction filings, newest first: non-derivative and derivative transaction legs, post-transaction holdings, owner roles (director/officer/10% owner), footnotes, and amendment (4/A) links. Numeric values are strings exactly as filed; every object carries 'accession' and 'filed_date'. Filter by issuer ticker, CIK, form_type, or since-date. Returns a {data, total, limit, offset} envelope for paging. Hosted and already normalized — no EDGAR crawling, parsing, or local install needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoSEC CIK number, digits only (leading zeros optional).
limitNoRows to return (max 25 on this endpoint).
sinceNoOnly filings filed on/after this date (YYYY-MM-DD).
untilNoOnly filings filed on/before this date (YYYY-MM-DD) — with since, a fixed reproducible window.
offsetNoRows to skip — page through 'total' with limit+offset.
tickerNoIssuer ticker symbol as filed, e.g. KMI. Case-insensitive exact match.
form_typeNo4 = original filing, 4/A = amendment.

TDQS

A4.5/5.0
Behavior5/5

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

Even with readOnlyHint=true and destructiveHint=false, the description adds substantial behavioral context: newest-first ordering, string-typed numeric values, mandatory accession/filed_date fields, the pagination envelope, and the hosted/normalized nature of the data. This goes well beyond what the annotations or schema convey.

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?

Every sentence carries value: the first defines scope and contents, the second covers data-type semantics, the third lists filters, the fourth explains pagination, and the fifth removes integration worries. No redundant restating of parameter names or annotations.

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?

For a tool with no output schema and several filter parameters, the description provides a complete mental model: what is returned, in what order, in what shape, how paging works, and what is already handled for the caller. Nothing an agent needs to decide whether and how to call it is missing.

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 documents every parameter. The description reinforces the filter-by-ticker/CIK/form_type/since-date framing and the paging envelope, but it does not add meaning beyond the schema for individual parameters. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('List normalized SEC Form 4 insider-transaction filings'), then details exactly what payload elements are included. The plural 'filings' plus the list-and-paging framing clearly separates this from the sibling get_insider_filing without needing to open schemas.

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 description clearly states what this tool is for — listing and filtering normalized Form 4 filings — and enumerates the available filter dimensions. It does not explicitly name an alternative or say 'for a single filing use get_insider_filing', so it stops just short of full when/when-not guidance.

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

All filingpulse toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: corporate events, insider filings, IPO registrations, dataset status, and schema. The pairings of list/fetch for insider filings and registrations follow a clear pattern, so there is no meaningful overlap.

Naming Consistency5/5

All seven tools use a consistent get_* prefix with a clear object or dataset name. The naming is uniform and predictable, making the tool surface easy to navigate.

Tool Count5/5

Seven tools is well-scoped for a read-only SEC filing query service. Each tool earns its place, covering list, fetch, status, and schema needs without redundancy or bloat.

Completeness4/5

The Form 4 and registration domains have both list and single-record fetch capabilities, and dataset status/schema cover operational needs. A minor gap is that 8-K corporate events have no single-event fetch by accession, and IPO registration listing lacks explicit filter options beyond the envelope.

Resources