Skip to main content
Glama

get_bill_text

Retrieve available versions of a US bill, such as Introduced, Engrossed, or Enrolled, with PDF, HTML, and XML download links for each text version.

Instructions

List available text versions (Introduced, Engrossed, Enrolled, etc.) with PDF/HTML/XML download links for a bill.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
billIdNo
numberNo
congressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully clarifies that the tool lists versions and returns download links rather than the bill text itself, which is a real disclosure. However, it says nothing about permissions, pagination, ordering of versions, or what happens when a bill has no published text, leaving significant gaps for a read operation against an external legislative API.

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?

A single front-loaded sentence, with the output content (version names and link formats) stated immediately after the verb. No filler or redundancy.

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?

The tool takes four loosely defined identifier parameters with no schema documentation and offers no output schema, yet the description only covers what is returned at a high level. The critical missing piece is how to resolve a bill across congress, type, number, and billId, which is exactly where an agent would fail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters (type, billId, number, congress), and the description adds no meaning to any of them. It never explains that congress/type/number jointly identify a bill or how billId relates to those fields, so an agent must guess the identifier scheme.

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 uses a specific verb ('List') and a well-defined resource ('available text versions ... for a bill'), and even names the version types (Introduced, Engrossed, Enrolled) and formats (PDF/HTML/XML). It implicitly separates itself from get_bill_details by scoping to version files rather than metadata, though it never names a sibling explicitly.

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?

Usage is only implied: an agent can infer this is the tool for retrieving bill document versions, but the description gives no conditions, no exclusions, and no instruction on when to prefer get_bill_details or get_public_law_text instead. No prerequisites for identifying the target bill are stated.

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