Signal8

Get Politicians

get_politicians

Read-only

List and search congressional politicians who have STOCK Act trading disclosures. Filter by party (D/R/I), state, or search by name. Returns paginated results with trade counts, last trade date, and net buy/sell direction over the trailing 12 months.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_politicians"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return (default: 10, max: 100)
`party`	No	Filter by party: 'D' (Democrat), 'R' (Republican), 'I' (Independent)
`state`	No	Filter by US state (2-letter code, e.g. "CA", "TX")
`offset`	No	Pagination offset (default: 0)
`search`	No	Search by politician name (partial match)
`sortBy`	No	Sort field (default: 'last_trade')
`sortOrder`	No	Sort direction (default: 'desc')

Output Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedJun 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / limit / description

Added value: +"Maximum results to return (default: 10, max: 100)"

addedInput schema / properties / offset / description
```
Added value: +"Pagination offset (default: 0)"
```

addedInput schema / properties / party / description

Added value: +"Filter by party: 'D' (Democrat), 'R' (Republican), 'I' (Independent)"

addedInput schema / properties / search / description

Added value: +"Search by politician name (partial match)"

addedInput schema / properties / sortBy / description

Added value: +"Sort field (default: 'last_trade')"

addedInput schema / properties / sortOrder / description
```
Added value: +"Sort direction (default: 'desc')"
```

addedInput schema / properties / state / description

Added value: +"Filter by US state (2-letter code, e.g. \"CA\", \"TX\")"

removedOutput schema / required
```
Removed value: -[
-  "data"
-]
```

Changed1 schema field changedJun 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {}
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedJun 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to restate safety. It adds useful behavior beyond the structured fields: pagination, the result payload (trade counts, last trade date, net buy/sell direction), and the 12-month trailing window underlying the direction metric.

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?

Three short sentences, front-loaded with purpose, then filters, then return shape. No filler and no repetition of schema-level defaults.

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?

With an output schema present, the description needn't explain return structure in full, and annotations cover the safety profile. It gives enough to call the tool correctly (filters, pagination), though it doesn't hint at result set size or how the trailing-12-month window interacts with sorting by last_trade.

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 party codes, 2-letter state, partial-name search, limit, offset, and sorting are all documented in the schema. The description echoes the filter dimensions but adds no format or behavior detail the schema lacks, making the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (list/search) and resource (congressional politicians with STOCK Act disclosures), plus what the results contain. That scoping detail distinguishes it from sibling directory tools like get_politician_detail or get_politicians_most_active without naming them explicitly, which keeps it just short of a 5.

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?

Usage is implied: this is the entry-point directory for finding politicians by party, state, or name. There is no explicit when-to-use versus siblings (get_politician_detail, get_politicians_most_active, get_politician_donors) and no stated exclusions, leaving routing to inference.

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

All Signal8 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.