Open Fec

Candidate Financials

candidate_financials

Read-onlyIdempotent

Get campaign finance summary for a candidate by their FEC candidate ID (e.g., "P80001571"). Returns total receipts, disbursements, cash on hand, individual contributions, PAC contributions, and loans. Use search_candidates first to find the candidate ID.

Input Schema

TableJSON Schema

Name	Required	Description
`cycle`	No	Election cycle year (e.g., 2024). Defaults to most recent.
`_apiKey`	Yes	OpenFEC API key
`candidate_id`	Yes	FEC candidate ID (e.g., "P80001571")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cycles`	Yes	Financial summary for each election cycle
`candidate_id`	Yes	FEC candidate ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-open-fec-api-key",
-    "candidate_id": "P80001571"
-  },
-  {
-    "_apiKey": "your-open-fec-api-key",
-    "candidate_id": "P80001571",
-    "cycle": 2024
-  }
-]New value: +[
+  {
+    "candidate_id": "P80001571"
+  },
+  {
+    "candidate_id": "P80001571",
+    "cycle": 2024
+  }
+]

First observedJun 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds value by specifying the exact data returned (total receipts, disbursements, cash on hand, individual contributions, PAC contributions, loans), which is behavioral context beyond the annotations.

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?

The description is a single, well-structured sentence that front-loads the core function, includes an example, and lists return fields concisely. No wasted words.

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?

The tool has an output schema (per context) and annotations cover safety. The description adds the return fields, the prerequisite step, and the default cycle behavior. It lacks explicit mention of error handling or pagination, but those are not critical for a simple summary tool and may be in the output schema.

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% – all parameters are documented. The description adds an example ID and notes the default for cycle, but these are minor additions. Per the baseline for high schema coverage, a 3 is appropriate.

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 states a clear verb ('Get') and resource ('campaign finance summary for a candidate'), includes an example ID, and lists the specific data fields returned. It clearly distinguishes this from committee_financials by focusing on candidates, even though it doesn't explicitly name the sibling.

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 instructs to use search_candidates first to obtain the candidate ID, which is a direct prerequisite. This tells the agent exactly when and how to use this tool, and implicitly when not to (without a candidate ID).

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

All Open Fec 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.