Skip to main content
Glama

search_congress_bills

Search Congress.gov for bills and resolutions by keyword, with optional Congress number and result limit filters. Use it to find relevant federal legislation.

Instructions

Search for bills and resolutions in Congress.gov. When TYPESAFE_API_KEY is set, only high-confidence Jev matches are returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_congress_bills"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (max 50)
queryYesSearch query for bills (e.g., 'immigration', 'healthcare', 'infrastructure')
congressNoCongress number (e.g., 118 for current Congress)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose one genuinely useful trait — results are conditionally filtered to 'high-confidence Jev matches' when TYPESAFE_API_KEY is set — but 'Jev' is undefined, and there is no mention of auth requirements, rate limits, result ordering, or pagination.

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?

Two short sentences with the core purpose front-loaded and no filler. The only structural flaw is that the conditional-filter sentence uses unexplained vocabulary instead of clarifying the tool's behavior.

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?

For a three-parameter search tool with a fully documented schema and no output schema, the definition covers the essential purpose. The unresolved 'Jev matches' concept and the absence of ranking or result-shape hints are the remaining gaps, but neither blocks correct invocation.

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 description coverage is 100%, so all three parameters (query, limit, congress) are already documented with types, bounds, and defaults. The description adds no syntax, format, or matching-behavior detail for the query parameter beyond what the schema states, so the baseline of 3 applies.

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 first sentence states a specific verb and resource ('Search for bills and resolutions in Congress.gov'), which is enough for an agent to distinguish it from sibling tools like get_bill_details or get_recent_bills. The second sentence muddies it by introducing the undefined term 'Jev matches', which the reader cannot resolve from context.

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 when-to-use guidance is given and no alternative is named. An agent cannot tell from this description whether to call search_congress_bills, get_recent_bills, or search_all_legal for a given legislative query, nor whether congress or limit matter for typical use.

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