Skip to main content
Glama
psalzman

MCP OpenFEC Server

by psalzman

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENFEC_API_KEYYesYour OpenFEC API key obtained from api.data.gov

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_candidateC

Get detailed information about a candidate

get_candidate_financialsC

Get financial data for a candidate

search_candidatesC

Search for candidates by name or other criteria

get_committeeC

Get detailed information about a committee

get_candidate_contributionsC

Get individual contributions for a candidate

get_filingsC

Retrieve official FEC filings with filters

get_independent_expendituresC

Get independent expenditures supporting or opposing candidates

get_electioneeringC

Get electioneering communications

get_party_coordinated_expendituresD

Get party coordinated expenditures

get_communication_costsC

Get corporate/union communication costs

get_audit_casesC

Get FEC audit cases and findings

get_bulk_downloadsB

Get links to bulk data downloads

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 12 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting specific FEC data types like candidates, committees, contributions, expenditures, filings, and downloads. There is no overlap in functionality—tools like get_candidate, get_committee, and get_filings serve separate resources, and even related tools like get_candidate_contributions and get_candidate_financials focus on different aspects of candidate data.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, starting with 'get_' or 'search_' followed by a specific noun phrase (e.g., get_candidate, search_candidates, get_audit_cases). This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming style.

Tool Count5/5

With 12 tools, the server is well-scoped for accessing U.S. Federal Election Commission data, covering key areas like candidates, committees, financials, expenditures, and filings. Each tool serves a distinct data retrieval function, avoiding bloat while providing comprehensive coverage for the domain.

Completeness4/5

The tool set offers strong coverage for retrieving FEC data, including candidates, committees, financials, expenditures, filings, and bulk downloads. A minor gap exists in update or management operations (e.g., no create or modify tools), but this is reasonable for a read-only data access server focused on public records, and agents can work effectively with the provided retrieval functions.

Maintenance

ActivityInactive
ResponsivenessNo issues