Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Politician Donors

get_politician_donors
Read-only

Retrieve a paginated list of campaign donors for a politician, including individuals and PACs, with details like name, amount, and employer. Filter by type, cycle, and sort by amount or date.

Instructions

Get the paginated list of campaign donors (individuals and PACs) for a single politician across one election cycle. Returns donor name, amount, type, employer/occupation (individuals), and committee details (PACs). Use this when a user asks "who donated to " or wants the full donor list. For a quick top-10 + cycle totals overview, use get_politician_donor_summary instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesPolitician URL slug (e.g., "sen-nancy-pelosi")
typeNoFilter by donor type: 'individual', 'pac', or 'all' (default: 'all')
cycleNoElection cycle as 4-digit year (e.g. "2024"). Defaults to most recent cycle.
limitNoMaximum results to return (default: 50, max: 100)
offsetNoPagination offset (default: 0)
sortByNoSort field: 'amount' (default), 'date', or 'name'
minAmountNoMinimum contribution amount in USD (filters out small donors)
sortOrderNoSort direction (default: 'desc')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and description aligns (no write actions). The description adds context about pagination and the specific data fields returned (donor name, amount, type, etc.), which is helpful but not excessive.

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 dense sentences: first defines the tool's core action and output, second provides clear usage guidance with sibling comparison. No 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?

Given output schema existence and 8 parameters, the description captures the primary use case and differentiates from a sibling. It doesn't cover all edge cases or defaults, but those are addressed in the schema. Reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by summarizing output fields (e.g., employer/occupation for individuals, committee details for PACs) that are not in the schema, and implies filtering capabilities. This enriches understanding beyond the parameter 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 it retrieves paginated campaign donors for a single politician, specifying the resource and verb. It distinguishes from get_politician_donor_summary by noting that this tool provides a full list rather than a summary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool (when user asks for full donor list) and when to use the alternative (quick top-10 summary). Names the sibling tool get_politician_donor_summary.

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