Skip to main content
Glama
sh-patterson

fec-mcp-server

get_disbursements

Retrieve itemized campaign expenditures, showing payment recipients, amounts, and purposes. Filter by amount to analyze significant spending patterns.

Instructions

Retrieve itemized expenditures (Schedule B) made by a campaign committee. Shows payment recipients, amounts, and stated purposes. Supports filtering by amount for researching significant spending patterns and campaign finance transparency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
committee_idYesFEC committee ID (e.g., "C00401224")
min_amountNoMinimum disbursement amount to filter (default: $1,000)
two_year_transaction_periodNoTwo-year period (e.g., 2024 covers 2023-2024).
cycleNoAlias for two_year_transaction_period to align with finance cycle filters.
purposeNoFilter by disbursement purpose keyword (e.g., "CONSULTING", "MEDIA")
include_notableNoInclude flagged-first notable analysis block in output (default: true)
fuzzy_thresholdNoFuzzy match confidence threshold for reference list matching (default: 90)
limitNoNumber of results to return (default: 20, max: 100)
sort_byNoSort results by "amount" (descending) or "date" (most recent first)amount
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It correctly portrays the tool as read-only ('Retrieve'), but omits any mention of authentication, rate limits, or whether any state changes occur. While 'Retrieve' is suggestive, an explicit safety statement would improve transparency.

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 consists of two short sentences, each serving a clear purpose: first to state the action and resource, second to explain utility. It is front-loaded and free of unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters and no output schema, the description provides a high-level overview but does not detail the response structure or pagination. An agent might need to infer the output format. The description is adequate but not fully comprehensive.

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 coverage is 100%, fulfilling the baseline. The description adds only generic value ('filtering by amount') beyond what the schema's parameter descriptions already convey. No additional parameter-specific context is provided.

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 uses a specific verb ('Retrieve') and resource ('itemized expenditures (Schedule B)'), clearly distinguishing from sibling tools like get_receipts or get_independent_expenditures. It also lists the key data fields (recipients, amounts, purposes), leaving no ambiguity about the tool's function.

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?

The description mentions 'researching significant spending patterns and campaign finance transparency' as a use case, but does not provide explicit guidance on when to avoid this tool or compare it with alternatives like get_committee_finances or get_independent_expenditures. The usage context is implied, not articulated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sh-patterson/fec-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server