Skip to main content
Glama

us-lobbying-mcp-server

Uslobbying Search Lobbyists

uslobbying_search_lobbyists
Read-onlyIdempotent

Find lobbyists by name or registrant in mode search, then retrieve filing-scoped evidence with mode activity, lobbyist_id and filing_year. Pass an evidence filing_uuid to uslobbying_search_filings for the complete filing. Covered positions are disclosed text, not verified present employment. Activity mode checks the requested lobbyist locally. Follow next_cursor for all results.

Input Schema

NameRequiredDescriptionDefault
modeNosearch (default) finds identities by name or registrant; activity requires lobbyist_id and filing_year. Omit with cursor.
nameNoLobbyist identity name substring.
cursorNoContinue the original scope; other query fields may be omitted.
client_idNoOptional activity client relationship record ID from candidates[].id in uslobbying_get_client_profile resolve mode; candidates[].client_id is secondary.
max_pagesNoSource pages per call; positive integers clamp to five, default one for discovery, five for analysis.
page_sizeNoUpstream rows per page; positive integers clamp to 25, default 25.
filing_yearNoRequired report year in activity mode.
lobbyist_idNoRequired in activity mode.
record_pathNoJSON Pointer to a stored value; empty selects the root.
record_limitNoMaximum object entries or array items, clamped to 25; text fragments use the response byte budget.
record_handleNoTenant/tool-bound deferred record handle.
record_offsetNoKey, item or Unicode-code-point offset.
registrant_idNoRegistrant identity ID.
registrant_nameNoRegistrant identity name substring.
covered_positions_onlyNoActivity only: require this lobbyist’s nonblank covered-position disclosure.

Output Schema

NameRequiredDescriptionDefault
modeNoResolved operation.
errorNoPresent when the call failed. Absent on success.
offsetNoFinal record delivery offset.
sourceNoOfficial source system.
noticesNoLimitations and success notices.
coverageNoAcquisition progress, independent of delivery.
evidenceNoMatched filing-based participant evidence in activity mode.
lobbyistsNoComplete identity records in search mode.
truncatedNoMore of the parent value remains available through record windows.
attributionNoRequired verbatim attribution for LDA data.
next_cursorNoNext acquisition or output window cursor.
retrieved_atNoRetrieval ISO timestamp.
record_windowNoLossless stored parent window.
total_recordsNoExact final record count when known.
record_handlesNoDeferred complete parents.
retrieval_toolNoTool that retrieves this parent.
delivery_limitsNoClamped controls for this call; an empty map means no clamp. Immediate cursor replay retains its original values.
output_completeNoWhether all result rows have been delivered.
records_deferredNoOversized parents available through handles.
records_returnedNoComplete records delivered in this window.
cursor_expires_atNoContinuation expiry ISO timestamp.
effective_filtersNoNormalized effective scope.
snapshot_source_urlsNoOfficial snapshot URLs.
snapshot_retrieved_atNoFARA snapshot retrieval timestamp.
snapshot_last_modifiedNoUpstream Last-Modified header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already cover read-only, open-world, and idempotent behavior, and the description adds useful caveats: covered positions are disclosed text rather than verified employment, activity mode checks the requested lobbyist locally, and cursors should be followed. It does not discuss rate limits or auth requirements, but the annotation set reduces that burden.

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?

The description is dense but front-loaded and free of filler. The caveat about covered positions is relevant, though the overall wording is somewhat compressed and could be easier to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, annotations, and output schema, the description supplies the key operational context an agent needs: mode selection, required activity inputs, filing handoff, disclosure caveat, and pagination behavior.

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 description coverage is 100%, so the schema already defines all 15 parameters. The description still adds cross-parameter meaning by explaining mode-dependent requirements and the cursor-based continuation pattern, which goes beyond isolated 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 gives a specific verb and resource, "Find lobbyists by name or registrant," and clearly separates the two operating modes, search and activity. It also distinguishes this from uslobbying_search_filings by explaining the handoff for complete filings.

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 states that search is the default mode and that activity requires lobbyist_id and filing_year, and it names uslobbying_search_filings as the alternative for complete filing evidence. It does not explicitly describe when not to use this tool versus other siblings such as uslobbying_get_client_profile.

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.