Skip to main content
Glama

Get Super PAC Organisation Donor Totals

super_pac_donors_summary
Read-onlyIdempotent

Totals from the Super PAC Donors Register, built from the FEC's bulk files: organisation contributions to super PACs and hybrid PACs for the 2025-26 and 2023-24 cycles, with rows, names as filed, named donors, the reviewed share and each FEC bulk file's date, and the change over the same date window in both cycles; organisation money by reviewed class, with issue and social-welfare groups split between those an exact IRS Exempt Organizations record matches and those whose status was not matched, beside companies, unions, trade associations, committees, tribal governments and other organisations; withheld and unreviewed strings as counts and amounts only; itemized contributions from individuals reported directly to these committees, counted only, beside organisation money on that exact basis, with conduit pass-through rows (ActBlue, WinRed) shown apart and excluded from every total; sectors and the largest recipient committees as the register lists them; the lag line; and the register's headlines with their basis. Organisation, committee and individual money into super PACs are three measures, each labelled and never combined into one figure. Organisation money is not corporate money: every total states its class. Super PACs and hybrid PACs are named exactly as the FEC committee master lists them, with their committee ids and no party or candidate label; a contribution to a super PAC is not a contribution to a candidate. The word nonprofit appears only on a record an exact IRS Exempt Organizations match carries, shown with that record; other issue and social-welfare groups read organisation (status not matched). Every answer carries the register's question note: these records show contributions reported to the FEC; they do not show what any donor received or intended, and they do not show cause and effect. Individual donors are counted, never named; withheld strings (trusts, holding vehicles, businesses named for a person, names resting on initials, unmatched committees) and unreviewed strings appear only as counts and amounts. Every answer quotes the FEC's restriction on the sale or use of individual contributor information (52 U.S.C. 30111(a)(4)) and the FEC bulk file date; the bulk file lags the committees' latest reports.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, non-destructive, and open-world, but the description adds substantial behavioral context beyond that: FEC bulk-file lag, withheld and unreviewed strings shown only as counts, individual donors never named, conduit pass-through rows excluded from totals, and required legal and basis notes on every answer. These disclosures materially help an agent understand the data's limitations and interpretation rules.

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

Conciseness2/5

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

The description is extremely long and dense, with multiple semicolon-chained clauses and repeated caveats about individual counts, withheld strings, organisation class, and naming. The opening sentence does front-load the core purpose, but the overall structure is hard to scan and contains redundancy that reduces conciseness.

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 zero inputs and no output schema, the description provides a rich accounting of what the summary includes: totals, rows, reviewed shares, bulk-file dates, cross-cycle changes, sector and recipient breakdowns, lag line, and headlines with basis. It does not describe the exact output structure or field layout, but for a no-parameter summary tool the substantive completeness is high.

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?

This tool takes zero parameters, so the parameter-semantics baseline is 4. There are no arguments for the description to explain, and the schema coverage is 100%.

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?

The description clearly states that this returns totals from the Super PAC Donors Register, built from FEC bulk files, and enumerates the aggregate dimensions it reports. It is specific about the resource and measures, but it does not explicitly distinguish itself from the sibling tools super_pac_donors_donor and super_pac_donors_recipient.

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 by the repeated emphasis on totals, summaries, and register headlines, suggesting it is for aggregate views rather than individual donor or recipient lookups. However, there is no explicit statement such as 'use this for totals; use super_pac_donors_donor for a specific donor' or any other when-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources