Skip to main content
Glama

Openfec Search Contributions

openfec_search_contributions
Read-onlyIdempotent

Search itemized individual contributions (Schedule A) or get aggregate breakdowns by size, state, employer, or occupation. Use to answer "who is funding this committee?" Itemized mode requires a committee_id. Aggregate by_size/by_state can use candidate_id instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoQuery mode. "itemized" returns individual contribution records (keyset pagination). "by_size" aggregates by contribution size bucket. "by_state" aggregates by contributor state. "by_employer" aggregates by employer. "by_occupation" aggregates by occupation.itemized
pageNoPage number (1-indexed) for aggregate modes. Explicit page is rejected in itemized mode, which paginates with cursor. Defaults to 1 for aggregates.
sortNoSort field. A "-" prefix sorts descending: use "-contribution_receipt_amount" for the largest receipts first, since the ascending form leads with the most negative rows (refunds, reattributions, redesignations). Itemized only; OpenFEC sorts by "-contribution_receipt_date" when omitted.
cycleNoTwo-year election cycle (e.g., 2024). Even years only. Defaults to current cycle for itemized mode.
cursorNoOpaque pagination cursor from a previous response of this tool. Itemized mode only (keyset pagination). Valid only for an otherwise-identical call — changing any other argument, including sort, rejects the cursor; omit it to start over.
max_dateNoLatest contribution date (YYYY-MM-DD). Itemized only.
min_dateNoEarliest contribution date (YYYY-MM-DD). Itemized only.
per_pageNoResults per page.
max_amountNoMaximum contribution amount in dollars. Itemized only.
min_amountNoMinimum contribution amount in dollars. Itemized only.
candidate_idNoCandidate ID (e.g., P00003392). Get IDs from openfec_search_candidates results. Enables by_size and by_state aggregates without a committee_id.
committee_idNoReceiving committee ID (e.g., C00703975). Get IDs from openfec_search_committees results.
is_individualNoOnly individual contributions (excludes committee-to-committee transfers). Itemized only.
contributor_zipNoZIP code prefix (starts-with match). Itemized only.
contributor_cityNoContributor city. Itemized only.
contributor_nameNoFull-text donor name search. Itemized only.
contributor_stateNoTwo-letter state code (e.g., CA). Itemized only.
contributor_employerNoFull-text employer search. Itemized only.
contributor_occupationNoFull-text occupation search. Itemized only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoQuery mode as the server resolved it. "by_size" and "by_state" resolve to "by_size_candidate" / "by_state_candidate" when scoped by candidate_id — a different endpoint with different row shapes — so read this rather than assuming the mode you sent.
countNoTotal matching contributions (itemized mode). Check count_is_approximate before quoting it as a figure.
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when the response needs context: how to broaden a search that matched nothing, which requested position ran out when contributions did match, or that the total is an estimate.
resultsNoContribution result set; itemized records or aggregate buckets depending on mode.
committeeNoThe committee every row in this response belongs to, carried once instead of repeated in each row. Present only when the query was scoped to a single committee_id; otherwise each row keeps its own committee object.
paginationNoPage-based pagination info (aggregate modes only).
totalCountNoTotal matching contributions or aggregate rows.
next_cursorNoPagination cursor for the next page of itemized results. Null when no more pages.
search_criteriaNoEcho of the search filters this call applied, as the server parsed them, minus paging arguments. Always present — compare it against what you sent to confirm every filter was honoured.
count_is_approximateNoTrue when OpenFEC reports count as an estimate rather than a tally, which it does on its highest-volume queries. Absent means the count is a tally.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / count / description
      Previous value: -"Total result count (may be approximate for itemized)."New value: +"Total matching contributions (itemized mode). Check count_is_approximate before quoting it as a figure."
    • addedOutput schema / properties / count_is_approximate
      Added value: +{
      +  "description": "True when OpenFEC reports count as an estimate rather than a tally, which it does on its highest-volume queries. Absent means the count is a tally.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when no contributions matched — echoes filters and suggests how to broaden."New value: +"Guidance when the response needs context: how to broaden a search that matched nothing, which requested position ran out when contributions did match, or that the total is an estimate."
    • addedOutput schema / properties / pagination / properties / count_is_approximate
      Added value: +{
      +  "description": "True when OpenFEC reports this count as an estimate rather than a tally, which it does on its highest-volume datasets. Absent means the count is a tally. An estimated count — and the pages derived from it — can be off by a wide margin; treat it as an order of magnitude, not a figure to quote.",
      +  "type": "boolean"
      +}
  2. Changed3 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `itemized_requires_committee_id`: Itemized mode invoked without a committee_id `aggregate_requires_committee_id`: by_employer or by_occupation aggregate without a committee_id `itemized_only_filters_in_aggregate_mode`: An itemized-only filter was supplied alongside an aggregate mode, which cannot apply it `inputs_not_applicable_to_mode`: The resolved Schedule A endpoint does not accept one or more explicitly supplied inputs Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `itemized_requires_committee_id`: Itemized mode invoked without a committee_id. `aggregate_requires_committee_id`: by_employer or by_occupation aggregate without a committee_id. `itemized_only_filters_in_aggregate_mode`: An itemized-only filter was supplied alongside an aggregate mode, which cannot apply it. `inputs_not_applicable_to_mode`: The resolved Schedule A endpoint does not accept one or more explicitly supplied inputs. Other values are possible when a failure originates below the handler."
    • removedOutput schema / properties / next_cursor / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / next_cursor / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed4 schema fields changed
    • removedInput schema / properties / page / default
      Removed value: -1
    • changedInput schema / properties / page / description
      Previous value: -"Page number (1-indexed) for the aggregate modes. Ignored in itemized mode, which paginates with cursor. Read pagination.pages in the response to see how many pages exist."New value: +"Page number (1-indexed) for aggregate modes. Explicit page is rejected in itemized mode, which paginates with cursor. Defaults to 1 for aggregates."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `itemized_requires_committee_id`: Itemized mode invoked without a committee_id `aggregate_requires_committee_id`: by_employer or by_occupation aggregate without a committee_id `itemized_only_filters_in_aggregate_mode`: An itemized-only filter was supplied alongside an aggregate mode, which cannot apply it Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `itemized_requires_committee_id`: Itemized mode invoked without a committee_id `aggregate_requires_committee_id`: by_employer or by_occupation aggregate without a committee_id `itemized_only_filters_in_aggregate_mode`: An itemized-only filter was supplied alongside an aggregate mode, which cannot apply it `inputs_not_applicable_to_mode`: The resolved Schedule A endpoint does not accept one or more explicitly supplied inputs Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "itemized_requires_committee_id",
      -  "aggregate_requires_committee_id",
      -  "itemized_only_filters_in_aggregate_mode"
      -]New value: +[
      +  "itemized_requires_committee_id",
      +  "aggregate_requires_committee_id",
      +  "itemized_only_filters_in_aggregate_mode",
      +  "inputs_not_applicable_to_mode"
      +]
  4. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "results",
      +      "mode",
      +      "search_criteria",
      +      "totalCount"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `itemized_requires_committee_id`: Itemized mode invoked without a committee_id `aggregate_requires_committee_id`: by_employer or by_occupation aggregate without a committee_id `itemized_only_filters_in_aggregate_mode`: An itemized-only filter was supplied alongside an aggregate mode, which cannot apply it Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "itemized_requires_committee_id",
      +            "aggregate_requires_committee_id",
      +            "itemized_only_filters_in_aggregate_mode"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "results",
      -  "mode",
      -  "search_criteria",
      -  "totalCount"
      -]
  5. Changed4 schema fields changed
    • addedOutput schema / properties / committee
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "The committee every row in this response belongs to, carried once instead of repeated in each row. Present only when the query was scoped to a single committee_id; otherwise each row keeps its own committee object.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / mode
      Added value: +{
      +  "description": "Query mode as the server resolved it. \"by_size\" and \"by_state\" resolve to \"by_size_candidate\" / \"by_state_candidate\" when scoped by candidate_id — a different endpoint with different row shapes — so read this rather than assuming the mode you sent.",
      +  "enum": [
      +    "itemized",
      +    "by_size",
      +    "by_state",
      +    "by_employer",
      +    "by_occupation",
      +    "by_size_candidate",
      +    "by_state_candidate"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / search_criteria / description
      Previous value: -"Echo of the search filters that produced this result set. Populated when results are empty to help diagnose why nothing matched."New value: +"Echo of the search filters this call applied, as the server parsed them, minus paging arguments. Always present — compare it against what you sent to confirm every filter was honoured."
    • changedOutput schema / required
      Previous value: -[
      -  "results",
      -  "totalCount"
      -]New value: +[
      +  "results",
      +  "mode",
      +  "search_criteria",
      +  "totalCount"
      +]
  6. Changed1 schema field changed
    • addedInput schema / properties / page
      Added value: +{
      +  "default": 1,
      +  "description": "Page number (1-indexed) for the aggregate modes. Ignored in itemized mode, which paginates with cursor. Read pagination.pages in the response to see how many pages exist.",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  7. Changed3 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor from a previous response. Itemized mode only (keyset pagination)."New value: +"Opaque pagination cursor from a previous response of this tool. Itemized mode only (keyset pagination). Valid only for an otherwise-identical call — changing any other argument, including sort, rejects the cursor; omit it to start over."
    • changedInput schema / properties / sort / description
      Previous value: -"Sort field. Itemized only."New value: +"Sort field. A \"-\" prefix sorts descending: use \"-contribution_receipt_amount\" for the largest receipts first, since the ascending form leads with the most negative rows (refunds, reattributions, redesignations). Itemized only; OpenFEC sorts by \"-contribution_receipt_date\" when omitted."
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "contribution_receipt_date",
      -  "contribution_receipt_amount"
      -]New value: +[
      +  "contribution_receipt_date",
      +  "-contribution_receipt_date",
      +  "contribution_receipt_amount",
      +  "-contribution_receipt_amount"
      +]
  8. Changed2 schema fields changed
    • removedInput schema / properties / candidate_id / pattern
      Removed value: -"^[HSP][0-9A-Z]+$"
    • removedInput schema / properties / committee_id / pattern
      Removed value: -"^C\\d+$"
  9. Changed3 schema fields changed
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Guidance when no contributions matched — echoes filters and suggests how to broaden.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / totalCount
      Added value: +{
      +  "description": "Total matching contributions or aggregate rows.",
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "results"
      -]New value: +[
      +  "results",
      +  "totalCount"
      +]
  10. Changed4 schema fields changed
    • changedInput schema / properties / candidate_id / description
      Previous value: -"Candidate ID. Enables by_size and by_state aggregates without a committee_id."New value: +"Candidate ID (e.g., P00003392). Get IDs from openfec_search_candidates results. Enables by_size and by_state aggregates without a committee_id."
    • addedInput schema / properties / candidate_id / pattern
      Added value: +"^[HSP][0-9A-Z]+$"
    • changedInput schema / properties / committee_id / description
      Previous value: -"Receiving committee ID (e.g., C00703975)."New value: +"Receiving committee ID (e.g., C00703975). Get IDs from openfec_search_committees results."
    • addedInput schema / properties / committee_id / pattern
      Added value: +"^C\\d+$"
  11. Changed9 schema fields changed
    • changedInput schema / properties / per_page / description
      Previous value: -"Results per page (max 100)."New value: +"Results per page."
    • addedInput schema / properties / per_page / maximum
      Added value: +100
    • addedInput schema / properties / per_page / minimum
      Added value: +1
    • changedInput schema / properties / per_page / type
      Previous value: -"number"New value: +"integer"
    • changedOutput schema / properties / pagination / properties / count / description
      Previous value: -"Total results."New value: +"Total result count."
    • changedOutput schema / properties / pagination / properties / page / description
      Previous value: -"Current page number."New value: +"Current page number (1-indexed)."
    • changedOutput schema / properties / pagination / properties / pages / description
      Previous value: -"Total pages."New value: +"Total number of pages."
    • changedOutput schema / properties / results / description
      Previous value: -"Contribution records (itemized) or aggregate rows."New value: +"Contribution result set; itemized records or aggregate buckets depending on mode."
    • changedOutput schema / properties / results / items / description
      Previous value: -"A contribution record (itemized entry) or an aggregate row."New value: +"Itemized contribution record (mode=itemized) or aggregate row (mode=by_size, by_state, by_employer, by_occupation)."
  12. Changed1 schema field changed
    • addedOutput schema / properties / results / items / description
      Added value: +"A contribution record (itemized entry) or an aggregate row."
  13. Changed4 schema fields changed
    • addedOutput schema / properties / results / items / properties
      Added value: +{}
    • removedOutput schema / properties / results / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / search_criteria / properties
      Added value: +{}
    • removedOutput schema / properties / search_criteria / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  14. First observed

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint and idempotentHint annotations already establish the safety profile, and the description adds mode constraints rather than new operational behavior such as pagination or response quirks. That is useful but modest, matching the baseline for a read-style tool with annotations present.

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?

Three sentences with no filler: mode list, use case, and mode-specific ID requirement are front-loaded and each sentence carries information. The natural-language breakdown names map directly to the mode enum values.

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?

For a 19-parameter tool the description plus fully documented schema and output schema cover the call correctly, including the critical committee_id requirement. It leaves by_employer/by_occupation funding requirements implicit ('by_size/by_state can use candidate_id instead' implies the others need committee_id), a minor gap.

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?

Input schema coverage is 100%, so the description does not need to enumerate parameters; the main text adds only a couple of high-level relationships (itemized requires committee_id; by_size/by_state can use candidate_id). This earns the baseline 3 but no higher because most parameter meaning is already in the schema.

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?

Description opens with a specific action and resource: 'Search itemized individual contributions (Schedule A) or get aggregate breakdowns' and ties it to a concrete user intent ('who is funding this committee?'). This separates it from sibling tools that handle filings, disbursements, or expenditures.

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 clear context for when to use the tool and mode-specific selectors: itemized requires committee_id, while by_size/by_state can use candidate_id instead. It does not explicitly name exclusions or alternatives such as search_disbursements for spending questions, so it stops short of full routing 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.