Skip to main content
Glama

get_fec_campaign_finance

Read-only

Federal campaign finance activity — PAC committees, total political disbursements, receipts, and political footprint signal. Source: FEC electronic filings. Use for political risk monitoring and PAC compliance. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.10 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "get_fec_campaign_finance"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Adds genuinely useful context beyond the annotations: data provenance (FEC electronic filings), a per-call price of $0.10 USDC, and an attestation/verification URL. Nothing contradicts readOnlyHint=true and openWorldHint=true. It does not disclose result shape, coverage window, or freshness of filings.

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

Conciseness3/5

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

Purpose is front-loaded in the first sentence, but roughly half the text is payment and attestation boilerplate ('post-quantum signed settlement receipt', verify URL, price) that aids trust decisions more than tool selection. The core functional statement is efficient.

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 no output schema and no annotation detail beyond the safety profile, the description should say what comes back (totals, cycle years, committee breakdowns) and what 'name' resolves to. It instead spends its budget on provenance and pricing, leaving the call contract underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'name' has 0% schema description coverage, and the description only implies it refers to a PAC committee. It never says whether 'name' accepts a committee ID, a candidate name, or an employer/organization, nor how partial or fuzzy matching behaves.

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?

States a specific resource and scope: 'Federal campaign finance activity — PAC committees, total political disbursements, receipts, and political footprint signal,' plus the source (FEC electronic filings). None of the listed siblings cover campaign finance, so it is effectively distinguishable, though the description never says the retrieval key is a committee/entity name.

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?

Gives a use case ('political risk monitoring and PAC compliance') but no explicit when-not conditions and no named alternative for related needs such as lobbying or individual donor data. The agent knows roughly the domain but not the boundaries.

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