Skip to main content
Glama

Search US Congress bills or get one bill's status

congress
Read-only

US federal bills from Congress.gov (Library of Congress). Keyword search (q) runs over the 250 most recently updated bills of a Congress, since the API has no full-text search; each match gets its sponsor, status and latest action. A bill number (bill=hr1234-119) returns its cosponsor count, committees and up to 30 actions. Public domain. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "congress"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords that must all appear in the bill title
billNoA bill, e.g. hr1234-119 or s50-119 (type, number, Congress)
limitNoMax bills for q, 1-25, default 10
congressNoCongress number 93 to the current one (119), default current

Output Schema

NameRequiredDescriptionDefault
noteNo
queryNo
totalNo
sourceNo
resultsNo
scannedNo
returnedNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "note": {},
      +    "query": {},
      +    "results": {},
      +    "returned": {},
      +    "scanned": {},
      +    "source": {},
      +    "total": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the key operational caveat that 'q' searches only the 250 most recently updated bills because the API has no full-text search, plus the shape of each result. It also covers the payment requirement (x402/USDC) and that failed calls are not charged, which the annotations do not convey.

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 front-loaded with the resource and the two modes before the caveats, and every sentence carries information. The pricing sentence is dense but relevant to invocation decisions; the paragraph format makes it slightly harder to scan than a bulleted split of the two modes.

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

Completeness5/5

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

With an output schema present, the description needn't detail return values, and it still summarizes them per mode. Combined with the search-coverage limitation, the format of the bill identifier, and the cost model, an agent has everything needed to choose a mode and call it correctly.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: 'q' matches title words only within the 250 most recently updated bills, and 'bill' must be a type-number-Congress string such as hr1234-119. 'limit' and 'congress' are left entirely to the schema, so it does not fully compensate for the text but does enrich the two critical parameters.

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 states a specific resource (US federal bills from Congress.gov) and two distinct operations: keyword search via 'q' and single-bill lookup via 'bill=hr1234-119'. It also names what each mode returns (sponsor/status/latest action vs. cosponsors/committees/actions), so an agent can tell the two behaviors apart without inspecting the schema.

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 two modes are explicitly described with the selecting condition: use 'q' for keyword search, use a bill number like 'bill=hr1234-119' for a specific bill's status. It does not name any sibling tool as an alternative or state when not to use this one, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources