Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Politician Late Filers

get_politician_late_filers
Read-only

Identify politicians with late STOCK Act filings, showing trades disclosed more than 45 days after transaction, sorted by filing delay to reveal poor disclosure compliance.

Instructions

Get STOCK Act late filing violations -- trades where the disclosure was filed more than 45 days after the transaction (a legal violation). Sorted by filing delay descending. Useful for identifying politicians with poor disclosure compliance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback period in days (default: 180, max: 730)
limitNoMaximum results to return (default: 10, max: 50)
offsetNoPagination offset (default: 0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true, and description adds that results are sorted by filing delay descending. No contradictions; description complements annotations with sorting and legal violation context.

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?

Two concise sentences, front-loaded with key information: subject, criteria, sorting, and use case. No unnecessary words.

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?

Given the tool's simplicity and the presence of an output schema, the description provides sufficient context: purpose, filtering criterion, sorting, and practical use. No gaps.

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 parameters are already well-described. The description does not add additional meaning beyond the schema, meeting the baseline.

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?

Clearly identifies the tool as retrieving STOCK Act late filing violations, with specific criteria (disclosure >45 days after transaction) and sorting by filing delay. Distinguishes from siblings like get_politician_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?

States the tool is useful for identifying politicians with poor disclosure compliance. While not explicitly excluding alternatives, the specific focus on late filings provides clear context.

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