Signal8

Get Donor Aggregates

get_donor_aggregates

Read-only

Get market-wide campaign-finance rollups across every tracked politician for a cycle: total raised, top 10 individual donors, top 10 PACs, party/chamber/cycle splits, and a most-funded politician leaderboard. Answers questions like "who are the biggest donors in 2024?" or "which party raised more?".

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_donor_aggregates"
  }
}

Input Schema

Name	Required	Description
`cycle`	No	Election cycle as 4-digit year (e.g. "2024"). Defaults to most recent cycle.
`party`	No	Filter by party: 'D', 'R', or 'I'
`chamber`	No	Filter by chamber: 'senate' or 'house'

Output Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJun 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / chamber / description
```
Added value: +"Filter by chamber: 'senate' or 'house'"
```
- addedInput schema / properties / cycle / description
```
Added value: +"Election cycle as 4-digit year (e.g. \"2024\"). Defaults to most recent cycle."
```
- addedInput schema / properties / party / description
```
Added value: +"Filter by party: 'D', 'R', or 'I'"
```
- 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.9/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful fact that results are pre-aggregated rollups with fixed top-10 cutoffs rather than exhaustive lists, but says nothing about cost, rate limits, or freshness/staleness of the underlying finance data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence leads with the core verb and scope, followed by example questions that make the use case immediately recognizable. The enumeration of result contents is slightly long but each item is substantive; no filler phrases.

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 detail return values, and all three optional parameters are documented in the schema. What an agent needs to pick this over sibling donor/politician tools — market-wide scope and the kind of question it answers — is present, with only explicit alternative routing left out.

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% and two of the three parameters carry enums, so the schema already defines cycle format and allowed party/chamber values. The description only implies that these filters narrow the rollups (mentioning party and chamber splits and a cycle), adding no syntax or default behavior beyond the schema — the baseline 3 for fully documented schemas.

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 names a specific verb and resource ('Get market-wide campaign-finance rollups') and enumerates the concrete contents (total raised, top 10 individual donors, top 10 PACs, party/chamber/cycle splits, leaderboard). The phrase 'across every tracked politician' contrasts the market-wide scope with per-politician siblings like get_politician_donors and get_politician_donor_summary.

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?

It gives concrete example questions the tool answers ('who are the biggest donors in 2024?', 'which party raised more?'), which tells an agent when to reach for it. It stops short of explicitly naming the alternative tools to use for single-politician or institution-level questions, so the routing is inferred from the 'market-wide' scope rather than stated.

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.