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}