Skip to main content
Glama

Stratalize Intelligence

Get Fec Campaign Finance

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so safety is covered. The description adds genuinely new operational context: the upstream data source (FEC electronic filings), a per-call price of $0.10 USDC, and an attestation/verification path with a concrete URL. It still says nothing about result volume, freshness, or what happens when a name matches multiple committees.

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

Conciseness4/5

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

Three short sentences, front-loaded with what the tool returns and followed by usage, provenance, and cost. The attestation/verification sentence is closer to marketing boilerplate than invocation guidance, but it does encode a real cost signal, so it is not pure waste.

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, the description does its part by naming the returned data classes (committees, disbursements, receipts). However, for a paid, open-world lookup keyed on a single ambiguous name, it omits matching behavior, expected result granularity, and error/empty-result behavior — enough gaps to keep this at minimum-viable.

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?

Schema description coverage is 0% and the only parameter is an unconstrained free-text 'name' (2-200 chars). The description does not say whether this should be a committee name, a candidate name, an FEC ID, or an employer string, nor whether matching is exact or fuzzy. With one parameter carrying the entire query, that omission is a real gap.

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?

The description names a specific verb-resource pairing ('Federal campaign finance activity') and enumerates the data classes returned: PAC committees, total political disbursements, receipts, and political footprint signal. It also names the source (FEC electronic filings). It does not, however, clarify what entity the single 'name' input resolves to, so the scope of the lookup stays fuzzy.

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?

'Use for political risk monitoring and PAC compliance' gives a stated use context, which is more than nothing. But there is no when-not guidance, no mention of alternate tools for other disclosure data, and no prerequisites such as whether a paid USDC balance is required before calling.

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