Skip to main content
Glama
AiAgentKarl

political-finance-mcp-server

get_candidate_fundraising

Retrieve campaign fundraising data for a candidate: total receipts, disbursements, and cash on hand by candidate name and election year.

Instructions

Ruft Spendeneinnahmen und -ausgaben eines Kandidaten ab.

Args: candidate_name: Name des Kandidaten (z.B. "Biden", "Trump") election_year: Wahljahr (Standard: 2024)

Returns: Fundraising-Daten: Einnahmen, Ausgaben, Cash-on-Hand

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
candidate_nameYes
election_yearNo
Behavior3/5

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

No annotations exist, so the description must cover behavioral traits. It implies a read operation and lists return fields, but omits details like error handling, rate limits, or authentication needs. The description is adequate but not rich.

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 is very concise with a clear structure: purpose sentence, Args with examples, and Returns. Every sentence adds value with no 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?

For a simple retrieval tool with two parameters and no output schema, the description covers the basics but lacks error context or scope details. It is minimally complete.

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

Parameters4/5

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

Schema coverage is 0%, so the description adds essential meaning: examples for candidate_name ('Biden', 'Trump') and a default for election_year (2024). This compensates well for the lack of schema descriptions.

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 clearly states the tool retrieves fundraising income and expenses for a candidate, using specific verbs and specifying the resource. It distinguishes from siblings like 'get_pac_spending' or 'get_campaign_finance_summary' by focusing on candidate-level fundraising.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives. With five sibling tools, explicit usage context is missing.

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/AiAgentKarl/political-finance-mcp-server'

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