Skip to main content
Glama

get_bill_details

Fetch live Congress.gov bill metadata—sponsors, latest action, policy area, and linked endpoints—by bill ID or congress, type, and number to identify and track legislation.

Instructions

Fetch live bill metadata from the Congress.gov API (sponsors, latest action, policy area, linked endpoints). Identify the bill by billId (e.g. 's1582-119', 'hr3633-119') OR by explicit congress+type+number.

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_bill_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoBill type (hr, s, hres, sres, hjres, sjres, hconres, sconres).
billIdNoCanonical id like 's1582-119' or 'hr3633-119'. Takes precedence over congress/type/number.
numberNo
congressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add real value by saying the metadata is 'live' from the upstream API and naming what comes back, but it is silent on failure behavior for unknown bill ids, freshness/caching, or rate limits.

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 sentences, front-loaded with the resource and payload, then the identification rule. Nearly every clause earns its place; only the repeated id example overlaps with the schema.

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?

With no output schema and no annotations, the description compensates reasonably by enumerating the returned metadata fields and the two identification paths. Gaps remain around error/not-found behavior and freshness guarantees, but the agent has enough to call it correctly.

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 50%: 'type' and 'billId' are documented in the schema, while 'number' and 'congress' have only bounds. The description adds the important structural semantics — that the three fields are used together as an alternative identifier and that billId takes precedence — but repeats the billId example format already present in the schema.

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?

States a specific verb and resource ('Fetch live bill metadata from the Congress.gov API') and enumerates the payload (sponsors, latest action, policy area, linked endpoints), which implicitly separates it from siblings like get_bill_actions and get_bill_text. It never names an alternative explicitly, so the differentiation is inferential rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description focuses on identification mechanics (billId OR congress+type+number) rather than on when to choose this tool over get_bill_actions, get_bill_text, or search_congress_bills. Usage is implied by the returned-field list, but there is no explicit when/when-not guidance.

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