Skip to main content
Glama
amurshak

CongressMCP-full

by amurshak

Congressional Committee Intelligence - Committee documents and activities

committee_intelligence

Retrieve and search congressional committee reports, prints, and meetings by Congress, chamber, committee, or keyword to support legislative research.

Instructions

Congressional Committee Intelligence - Professional access to committee documents and activities.

COMMITTEE REPORTS (7 operations):
• get_latest/by_congress/by_type, get_report_details/text_versions/content
• search_committee_reports - Advanced analytics with chunking support

COMMITTEE PRINTS (6 operations):
• get_latest/by_congress/by_chamber, get_print_details/text_versions
• search_committee_prints - Document intelligence with filtering

COMMITTEE MEETINGS (6 operations):
• get_latest/by_congress/by_chamber/by_committee, get_meeting_details
• search_committee_meetings - Process intelligence with scheduling data

REQUIRED PARAMETERS (the schema marks every parameter optional because
one shared schema covers every operation -- these operations fail
without the values below):
• congress -- get_committee_reports_by_congress,
  get_committee_prints_by_congress, get_committee_meetings_by_congress
• congress + chamber -- get_committee_prints_by_congress_and_chamber,
  get_committee_meetings_by_congress_and_chamber
• congress + report_type -- get_committee_reports_by_congress_and_type
• congress + report_type + report_number -- get_committee_report_details,
  get_committee_report_text_versions, get_committee_report_content
• congress + chamber + jacket_number -- get_committee_print_details,
  get_committee_print_text_versions
• congress + chamber + committee_code --
  get_committee_meetings_by_committee
• congress + chamber + event_id -- get_committee_meeting_details
(get_latest_committee_reports/prints/meetings and every search_*
operation need none of the above)

Key params: operation, congress, chamber, committee_code, report_type, event_id
Returns structured committee data with enhanced metadata and content chunking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo
limitNo
offsetNo
chamberNo
congressNo
event_idNo
keywordsNo
operationYes
chunk_sizeNo
conferenceNo
report_typeNo
chunk_numberNo
scheduled_toNo
to_date_timeNo
jacket_numberNo
report_numberNo
committee_codeNo
from_date_timeNo
scheduled_fromNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when success is false: the section-9 error envelope
successYesWhether the operation was successful
summaryYesHuman-readable summary of committee intelligence
insightsNoKey insights about committee activity
operationYesThe operation that was performed
activitiesNoCommittee activity results
results_countYesNumber of items returned (equals the populated list's length)
Install Server

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the shared-schema optionality trap and that operations will fail without required values, and it notes structured returns with metadata and chunking. It does not mention side effects, permissions, rate limits, or explicitly state that the operations are read-only.

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 long but well-organized with clear category headings, bullet lists, and a separated REQUIRED PARAMETERS section. Each section earns its place, and critical operational guidance is front-loaded. Some repetition of operation names exists, but it remains scannable.

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?

Given the unusual design of one shared schema over 19 operations, the description provides essential context: operation-to-parameter combinations, the fact that schema optionality is misleading, and that search/latest operations have different requirements. It does not cover value formats or deeper filtering semantics, but the output schema covers return structure and the operation guidance is strong.

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 0%, so the description must compensate. The mapping of congress, chamber, report_type, jacket_number, committee_code, and event_id to specific operations adds substantial meaning beyond the schema. It still does not define allowed values or formats for parameters like chamber, report_type, or date range fields, but the operation-dispatch guidance is highly valuable.

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 providing congressional committee documents and activities, and enumerates the operations by category (reports, prints, meetings). It does not explicitly distinguish itself from sibling tools such as get_committee_reports, which also deals with committee documents, so it falls short of full differentiation.

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 REQUIRED PARAMETERS section gives concrete operation-to-parameter mappings and warns that operations fail without the required values, which is strong usage guidance. It also clarifies that search and latest operations need none of those parameters. However, it does not address when to choose this tool over sibling tools like get_committee_reports.

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