Signal8 MCP Server

Official

by signal8ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get Politician Transactions

get_politician_transactions

Read-only

Retrieve paginated trade history for a politician, showing STOCK Act filings with ticker, transaction type, amount range, and filing delay. Includes summary of total buys, sells, and net value.

Instructions

Get paginated trade history for a specific politician. Returns individual STOCK Act disclosures with ticker, transaction type, amount range, filing delay, and late filing flag. Includes a summary with total buys/sells and net value.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Politician URL slug (e.g., "sen-nancy-pelosi")
`type`	No	Filter by transaction type: 'Purchase' or 'Sale'
`limit`	No	Maximum results to return (default: 50, max: 100)
`offset`	No	Pagination offset (default: 0)
`sortBy`	No	Sort field (default: 'date')
`sortOrder`	No	Sort direction (default: 'desc')

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true. The description adds behavioral context: paginated returns, STOCK Act disclosures, summary with buys/sells. No contradictions. Could mention rate limits or data freshness, but adequate.

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 sentences: first states purpose, second details output. No unnecessary words, front-loaded, every sentence earns its place.

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?

Has output schema, so return values are documented. Description covers key output fields and pagination. Could mention error handling or data freshness, but overall sufficient for a straightforward read 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 description coverage is 100%, so baseline is 3. The description hints at pagination (offset/limit) but does not add significant meaning beyond the schema. However, it mentions the output fields which indirectly relate to parameters.

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 it gets paginated trade history for a specific politician, with details on returned fields and a summary. It distinguishes itself from siblings like get_politician_recent_trades by focusing on full paginated history.

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 detailed trade history but does not explicitly state when to use this vs. alternatives or provide exclusions. Given many sibling politician tools, more guidance would be helpful.

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

Deploy Server