Skip to main content
Glama
adathouse
by adathouse

Search bills

search_bills

Search and list bills/resolutions using filters such as Congress, type, sponsor, date range, or latest action text. Results are paginated with adjustable page size.

Instructions

Search and list bills/resolutions with flexible filters. Use this for questions like 'bills recently introduced in the House', 'bills that became law recently' (latestActionContains: 'Became Public Law'), or 'bills that passed the Senate' (latestActionContains: 'Passed Senate'). Results are paginated; increase 'limit' (max 50) for more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
congressNoCongress number, e.g. 119 for the 119th Congress.
billTypeNoBill type code: HR, S, HJRES, SJRES, HCONRES, SCONRES, HRES, SRES.
originChamberNoChamber where the bill originated.
titleContainsNoCase-sensitive substring to match within the bill title.
latestActionContainsNoSubstring to match within the latest action text. Examples: 'Became Public Law', 'Passed House', 'Passed Senate', 'Referred to the Committee'.
introducedAfterNoOnly bills introduced on/after this date (YYYY-MM-DD).
introducedBeforeNoOnly bills introduced on/before this date (YYYY-MM-DD).
sponsorStateNoTwo-letter state code of the bill sponsor, e.g. 'CA'.
sponsorPartyNoParty of the bill sponsor, e.g. 'R', 'D', 'I'.
sponsorBioguideIdNoBioguide ID of the bill sponsor.
sortByNoField to sort by. Default: introducedDate.
sortOrderNoSort direction. Default: DESC (newest first).
limitNoMax results to return (1-50). Default 10.
afterNoRelay pagination cursor. Pass the `pageInfo.endCursor` from a previous result to fetch the next page.
Behavior3/5

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

With no annotations, the description carries full burden. It mentions pagination and limit max, but does not state read-only nature or any side effects. Adequate but could be more explicit about behavioral traits.

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

Conciseness5/5

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

Two sentences plus examples; front-loaded with purpose, no fluff. Every sentence earns its place.

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 14 parameters, no required, and no output schema, the description covers the essential usage and pagination. It could mention the return format, but is fairly complete for a list tool.

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 coverage is 100% with good descriptions; the description adds value through examples (e.g., latestActionContains: 'Became Public Law') but does not significantly augment parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search and list bills/resolutions with flexible filters' and provides concrete query examples, distinguishing this from sibling tools like search_actions (actions on bills) and get_bill (single bill).

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 explicitly gives usage examples (e.g., 'bills recently introduced in the House') and shows parameter combinations. It does not explicitly say when not to use or name alternatives, but the examples are clear enough.

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/adathouse/cdgmcp'

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