Skip to main content
Glama
lzinga

US Government Open Data MCP

lobbying_contributions

Read-only

Search campaign contributions by lobbyists to politicians, filterable by year, registrant name, or lobbyist name.

Instructions

Search campaign contributions made by lobbyists — shows which lobbyists donated to which politicians. Required under the LDA to disclose political contributions by registered lobbyists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filing_yearNoYear: 2020-2026
registrant_nameNoLobbying firm name
lobbyist_nameNoIndividual lobbyist name
page_sizeNoResults per page (default 20)
Behavior3/5

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

Annotations already declare readOnlyHint=true. Description adds context about searching and legal requirements under LDA but does not disclose additional behavioral traits like rate limits or output format. Acceptable but minimal added value.

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?

Two concise sentences that front-load the core purpose and legal context. Every sentence is informative without unnecessary detail.

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 simple search tool with no output schema, the description is mostly complete. It could benefit from mentioning pagination or default output behavior, but it adequately covers the main functionality.

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 covers all 4 parameters with descriptions (100% coverage). Description does not add any extra meaning or usage hints beyond what schema provides, meeting baseline expectations.

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?

Description clearly states the tool searches campaign contributions by lobbyists and shows who donated to whom, with a specific verb and resource. While it doesn't explicitly differentiate from sibling lobbying tools, the name and context make its purpose distinct.

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?

No explicit guidance on when to use this tool versus other lobbying tools (e.g., lobbying_search, lobbying_lobbyists). Description only states its function without providing selection criteria or exclusions.

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/lzinga/us-gov-open-data-mcp'

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