Skip to main content
Glama
amurshak

CongressMCP-full

Congressional Committee Intelligence - Committee documents and activities

committee_intelligence

Access congressional committee reports, prints, and meeting schedules. Retrieve structured legislative documents with advanced search, metadata, and content chunking capabilities.

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

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
operationYes
congressNo
chamberNo
committee_codeNo
limitNo
report_typeNo
report_numberNo
conferenceNo
chunk_numberNo
chunk_sizeNo
jacket_numberNo
event_idNo
keywordsNo
scheduled_fromNo
scheduled_toNo
sortNo
offsetNo
from_date_timeNo
to_date_timeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Without annotations, the description carries the full burden. It mentions 'content chunking' and 'enhanced metadata' which adds useful behavioral context, but omits critical safety information (read-only vs. destructive), rate limits, or authentication requirements implied by 'Professional access'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The structured bullet format for categories is helpful, but listing operation counts (e.g., '7 operations') without naming them wastes space. The 'Key params' section is good front-loading, though the opening title repetition is redundant.

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

Completeness2/5

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

Given the high complexity (19 parameters, polymorphic operation mode, 0% schema coverage), the description is insufficient. It categorizes operations but doesn't enumerate them or explain selection logic, leaving critical gaps for an agent attempting to construct valid invocations.

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

Parameters2/5

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

With 0% schema description coverage, the description fails to compensate adequately. While it lists 'Key params', it does not explain the crucial 'operation' parameter's valid values (the 19 sub-operations), nor explain chunking semantics, date formats, or parameter interactions required for this complex multi-mode tool.

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 provides access to committee documents and activities, breaking functionality into three distinct categories (Reports, Prints, Meetings). However, it fails to clearly articulate that this is a polymorphic tool where the 'operation' parameter selects between 19 distinct sub-operations, which is critical for correct invocation.

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 is provided on when to use this tool versus siblings like 'get_committee_reports' or 'search_committees', despite clear functional overlap. There is no explanation of how to select appropriate operations or prerequisites for using specific document retrieval modes.

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

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