Skip to main content
Glama

get_recent_bills

Retrieve recently introduced U.S. congressional bills by Congress number and result limit to track new legislation.

Instructions

Get the most recently introduced bills in Congress

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": "get_recent_bills"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (max 50)
congressNoCongress number (e.g., 118 for current Congress)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and does very little with it. It does not say how 'most recent' is ordered (introduction date vs. latest action), whether the feed is paginated or capped, or what happens when no congress is supplied; the read-only nature is only implied by the verb 'Get'.

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?

A single well-formed sentence with the key qualifier ('most recently introduced') front-loaded and no filler. It is efficient, though its brevity borders on under-specification rather than genuine conciseness.

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

Completeness2/5

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

For a simple two-parameter read tool the description could be shorter than for a mutation, but with no annotations and no output schema, the definition still leaves the core behavioral question—what 'recent' means and how results are ordered—unanswered.

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 both parameters (limit, congress) are already fully documented in the schema with defaults and bounds. The description adds no additional meaning about parameter interactions, such as whether congress defaults to the current Congress.

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 gives a specific verb ('Get') and resource ('most recently introduced bills in Congress'), which is clearly distinct from a keyword-based 'search_congress_bills'. It stops short of explicitly naming the sibling it differs from, so an agent must infer the distinction from the word 'recent'.

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?

There is no when-to-use guidance, no mention of when to prefer search_congress_bills, and no prerequisites or exclusions. The only signal is the word 'recent', which implies browsing rather than querying.

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