Govparse Government Data Gateway

sec_insiders_clusters

Where are corporate insiders buying or selling as a cluster? Search SEC Form 4 clusters — issuers where several distinct officers/directors/10%-owners transacted the same direction in a trailing 30- or 90-day window (buy=accumulation, sell=distribution). Filter by ticker, direction, window, minimum insiders, minimum value, or exchange. Returns issuer ticker/company/exchange, insider count, and total shares/value. Public SEC filings as filed — observational, not advice. [price: $0.05/row]

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	insider_count \| total_value \| txn_count \| last_txn_date :asc\|:desc. Default insider_count:desc.
`limit`	No	Max rows (default 25, cap 100).
`since`	No	Most recent transaction in the cluster on/after this date (YYYY-MM-DD).
`offset`	No	Rows to skip, for paging.
`ticker`	No	Issuer ticker(s), CSV.
`window`	No	Trailing window in days: 30 \| 90.
`exchange`	No	Listing exchange(s), CSV: NYSE, Nasdaq, OTC...
`direction`	No	buy (open-market purchase cluster) \| sell (open-market sale cluster).
`min_value`	No	Minimum total $ transacted in the window.
`issuer_cik`	No	SEC issuer CIK.
`min_insiders`	No	Minimum distinct insiders in the cluster (>= 2).

Schema Changelog

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

AddedJul 24, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of disclosure. It mentions the data is from public SEC filings, observational, not advice, and includes pricing per row. However, it does not explicitly state that the tool is read-only or has no side effects, nor does it discuss rate limits or caching.

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?

The description is concise (approximately 150 words) and well-structured: purpose statement first, followed by details on parameters, return fields, a disclaimer, and pricing. Every sentence adds value with no redundancy or fluff.

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 tool with 11 parameters, no output schema, and no annotations, the description is quite complete. It explains the cluster concept, filters, return fields (issuer ticker/company/exchange, insider count, total shares/value), and includes a disclaimer and pricing. It could be improved by providing an example output structure.

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% with all parameters having descriptions. The tool description adds value by summarizing the filterable parameters and return fields, but does not provide additional semantics beyond what the schema already offers.

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 searches for SEC Form 4 clusters of insider buying or selling, specifying the resource (SEC Form 4 clusters), action (search), and key details like time window and direction. It distinguishes from the sibling sec_insiders_transactions by focusing on clusters rather than individual transactions.

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 explains when to use the tool (to find clusters of insider activity) and lists available filters (ticker, direction, window, etc.). It does not explicitly state when not to use it or mention alternatives, but the context and sibling names imply the distinction.

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 tools Inspect

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

Need Help?