Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Congressional Records and Hearings - Legislative records, communications, and hearings

records_and_hearings

Retrieve congressional records, communications, and hearings by date, congress, chamber, or keywords; get full-text content and metadata for legislative research.

Instructions

Congressional Records and Hearings - Access legislative records, communications, and hearings.

CONGRESSIONAL RECORDS (3 operations):
• search_congressional_record/daily/bound - Search legislative records by date/volume

COMMUNICATIONS (8 operations):
• House: search_house_communications/requirements, get_details/matching
• Senate: search_senate_communications, get_senate_communication_details
• Committee: get_committee_communication_details

HEARINGS (5 operations):
• search_hearings, get_hearings_by_congress/chamber, get_hearing_details/content

REQUIRED PARAMETERS (the schema marks every parameter optional because
one shared schema covers every operation -- these operations fail
without the values below):
• congress -- get_hearings_by_congress
• congress + chamber -- get_hearings_by_congress_and_chamber
• congress + chamber + jacket_number -- get_hearing_details,
  get_hearing_content
• congress + communication_type + communication_number --
  get_senate_communication_details, get_house_communication_details
• congress + chamber + communication_type + communication_number --
  get_committee_communication_details
• requirement_number -- get_house_requirement_details,
  get_house_requirement_matching_communications
(search_congressional_record/daily/bound and every other search_*
operation need none of the above)

Key params: operation, year/month/day, keywords, congress, chamber, jacket_number
Returns structured record/hearing data with full text content and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNo
sortNo
yearNo
limitNo
monthNo
chamberNo
congressNo
keywordsNo
operationYes
issue_numberNo
to_date_timeNo
jacket_numberNo
volume_numberNo
from_date_timeNo
communication_typeNo
requirement_numberNo
communication_numberNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when success is false: the section-9 error envelope
itemsNoResults of other kinds (communications, requirements), as returned by Congress.gov
recordsNoCongressional Record results
successYesWhether the operation was successful
summaryYesHuman-readable summary of the results
hearingsNoHearing results
item_kindNoWhat `items` contains (communication, requirement, daily_record, bound_record, ...)
operationYesThe operation that was performed
results_countYesNumber of items returned (equals the populated list's length)
Install Server

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It explains the shared-schema quirk, states that operations fail without certain values, and mentions that it returns structured record/hearing data with full text content. It does not discuss pagination, authentication, or rate limits, but the read-only nature of the operations is strongly implied by the search/get operation names.

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 well-structured with clear section headers and bullet lists, and the required-parameters section earns its length because it resolves a critical schema inconsistency. It is longer than ideal and contains some redundancy and ambiguous shorthand, but the complexity of a multi-operation dispatcher tool justifies most of the detail.

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?

The description covers operation families, required parameter combinations, and return data, which is substantial for a tool with 17 params and 16 operations. However, exact operation-name derivation is not fully unambiguous from the slash notation, and several parameters remain undocumented. An agent could still struggle to construct a valid operation string with confidence.

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?

Schema description coverage is 0%, so the description must compensate. It does map required parameter combinations to specific operations and highlights key params, which is valuable. However, several schema params (sort, limit, from_date_time, to_date_time, issue_number, volume_number) are not explained, and the slash notation leaves exact operation string values ambiguous in places.

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 clearly identifies the tool as an access point for congressional records, communications, and hearings, and enumerates the operation families. It distinguishes this tool from bill/member/committee tools by its domain focus, though the slash-separated operation shorthand (e.g., search_congressional_record/daily/bound) creates some ambiguity about exact operation names.

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?

The description gives explicit guidance on which parameters are required for which operations, and warns that operations fail without them despite the schema marking all parameters optional. It does not explicitly route users to sibling tools, but the operation-family breakdown and required-parameter table provide strong within-tool usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/amurshak/congressMCP'

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