Skip to main content
Glama

Govparse Government Data Gateway

by io.govparse

sec_feed_insiders

Which public companies are insiders buying as a cluster right now? Bulk feed over SEC Form 4 open-market BUY clusters — issuers where several distinct officers/directors/10%-owners bought in a trailing 30- or 90-day window. Flat rows newest-first by the cluster's most recent buy, cursor-paginated up to 1000/page, filterable by ticker, exchange, min insiders, min value, window, or since. Every issuer is a public company with ticker and CIK. Observational filings as filed, never advice. [price: $0.05/row]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows per page (default 500, cap 1000).
sinceNoOnly clusters whose most recent buy is on or after this date (YYYY-MM-DD).
cursorNoOpaque page cursor — pass the previous page's next_cursor unchanged.
tickerNoIssuer ticker(s), CSV.
windowNoTrailing cluster window in days: 30 | 90. Default 90.
exchangeNoListing exchange(s), CSV: NYSE, Nasdaq, OTC...
min_valueNoMinimum total $ purchased across the cluster window.
min_insidersNoMinimum distinct insiders in the cluster (>= 2).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses key behaviors: newest-first ordering, cursor pagination up to 1000 rows, filter options, and that data is observational not advice. Does not cover rate limits, authentication, or error handling, but overall clear.

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?

The description is concise and front-loaded with the key question, packed with essential information. The single-sentence structure effectively communicates purpose and behavior without unnecessary fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should clarify return values. It mentions 'flat rows' with ticker and CIK but does not detail the full row structure. For an 8-parameter tool, the output format could be more explicitly described.

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 baseline is 3. The description adds context for parameters (e.g., window options, min_insiders threshold), but does not significantly enhance understanding beyond schema descriptions.

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 clearly states the tool's purpose: identifying public companies with insider buying clusters from SEC Form 4 filings. It explicitly distinguishes itself from siblings like sec_insiders_transactions by focusing on clusters of multiple insiders.

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?

The description implies usage for finding current insider buying clusters, but does not explicitly state when not to use this tool or contrast with alternatives like sec_insiders_clusters or sec_insiders_transactions. The context of siblings provides some guidance.

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

All Govparse Government Data Gateway 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 domain and specific action (e.g., FDA approvals vs clearances vs recalls; firmstanding business360 dossier vs search vs screen). Even overlapping concepts like 'business360' vs 'business360_lookup' are distinguished by input (UUID vs name+state). No two tools appear to do the same thing.

Naming Consistency5/5

All tools use a consistent lowercase snake_case pattern with domain prefix (e.g., fda_*, firmstanding_*, fmcsa_*, govcon_*). Action words (search, lookup, screen, feed, stats) follow predictable usage. The naming is uniform and easy to parse.

Tool Count4/5

38 tools is on the higher end but appropriate for a comprehensive government data gateway spanning multiple agencies and datasets. Each domain has a reasonable number of tools (e.g., FMCSA: 7, OFLC: 6). Could potentially be trimmed slightly, but overall well-scoped for the stated purpose.

Completeness5/5

The tool surface covers the major government data sources comprehensively: FDA (approvals, clearances, recalls), FMCSA (carrier census, safety, insurance, etc.), FSIS, DOJ/OFLC, OSHA/EPA/DOL enforcement, SEC insider filings, clinical trials, VA facilities/opportunities/vendors, and federal contracting. No obvious gaps for the stated gateway purpose.

Resources