Skip to main content
Glama
amurshak

CongressMCP-full

Congressional Bills - Comprehensive bill operations

bills

Search U.S. Congressional legislation using natural language identifiers like 'HR 1234'. Retrieve text, summaries, metadata, and track procedural actions including amendments, cosponsors, and committee progress.

Instructions

Comprehensive Bills Tool - All bill operations in one focused interface.

FLEXIBLE BILL IDENTIFICATION (NEW):
Use bill_id for natural language references like 'HR 1234', 'H.R. 1234, 118th Congress', 
'hr1234-118', 'S 456', etc. Automatically parses to congress/bill_type/bill_number.

CORE OPERATIONS:
• Search & Discovery: search_bills, get_bills, get_recent_bills
• Details & Metadata: get_bill_details, get_bill_titles, get_bill_subjects
• Text & Content: get_bill_text, get_bill_text_versions, get_bill_content
• Summaries: get_bill_summaries
• Relationships: get_bill_related_bills, get_bill_amendments
• Legislative Process: get_bill_actions, get_bill_committees, get_bill_cosponsors
• Date-Based: get_bills_by_date_range

Args:
    operation: Specific operation to perform (see list above)
    bill_id: Flexible bill reference (e.g., 'HR 1234', 'H.R. 1234, 118th Congress', 'hr1234-118')
             Automatically parsed to populate congress, bill_type, bill_number
    keywords: Search keywords for content and metadata
    congress: Congress number (118 for current, 119 for next)
    bill_type: hr, s, hjres, sjres, hconres, sconres, hres, sres
    bill_number: Specific bill number within type and congress
    limit: Results limit (max 250 for API compliance)
    sort: updateDate+desc (newest first) or updateDate+asc
    fromDateTime/toDateTime: Date range (YYYY-MM-DDTHH:MM:SSZ)
    version: Text version for content operations
    
Returns:
    Formatted results specific to requested operation
    
Examples:
    Using flexible bill_id:
    {"operation": "get_bill_details", "bill_id": "HR 1234"}
    {"operation": "get_bill_details", "bill_id": "H.R. 1234, 118th Congress"}  
    {"operation": "get_bill_details", "bill_id": "hr1234-118"}
    
    Traditional parameters still work:
    {"operation": "get_bill_details", "congress": 118, "bill_type": "hr", "bill_number": 1234}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
bill_idNo
keywordsNo
congressNo
bill_typeNo
bill_numberNo
limitNo
sortNo
formatNo
offsetNo
fromDateTimeNo
toDateTimeNo
days_backNo
versionNo
chunk_numberNo
chunk_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses useful behavioral traits: bill_id auto-parsing logic and the 250-result API limit. However, it fails to disclose read-only vs. destructive status, error handling behaviors, or rate limiting beyond the limit parameter.

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 description uses helpful structural headers (FLEXIBLE BILL IDENTIFICATION, CORE OPERATIONS) and front-loads the important flexible ID feature. However, the CORE OPERATIONS section is a lengthy uncategorized list that could be more concise, and the overall length is substantial relative to the information density.

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?

Given the tool has an output schema (not shown but indicated), the brief 'Returns' statement is acceptable. With 16 parameters and complex operation routing, the description covers the critical path well (bill identification) but leaves gaps in pagination (offset), text chunking (chunk_number/size), and alternative date filtering (days_back), preventing a higher score.

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%, requiring the description to compensate. It excellently documents bill_id formats (multiple examples), congress numbering (118/119), bill_type enumerations, sort options, and datetime formats. However, it completely omits 5 parameters: format, offset, days_back, chunk_number, and chunk_size, leaving significant gaps in the 16-parameter schema.

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 manages Congressional bills with specific operations (search, details, text, amendments, etc.) and categorizes them by function (Discovery, Metadata, Text, etc.). However, it doesn't explicitly distinguish when to use this tool versus the standalone 'amendments' sibling tool that appears to overlap with the get_bill_amendments operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on the two identification patterns (flexible bill_id vs. explicit congress/bill_type/bill_number parameters) with concrete examples. However, it lacks explicit 'when-to-use' guidance regarding sibling alternatives or prerequisites for specific operations.

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