Skip to main content
Glama

get_bill_documents

Read-only

Retrieve a bill's documents - text versions, fiscal notes, committee reports, and transmittal letters - with absolute URLs.

Instructions

List a bill's documents (bill text versions, fiscal notes, committee reports, transmittal letters) with absolute URLs.

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": {
      "bill": "<bill>"
    },
    "name": "get_bill_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYesBill number, e.g. 'HB 1', 'SB42', 'HJR 3'.
sessionNoSession, e.g. '2026', '2026GS', '2025S1'. Omit for the current general session.
max_charsNoCharacter budget for this response (500-20000). Defaults to the server setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description only needs to add operational context. It usefully states that URLs are absolute, but says nothing about ordering, whether all historical versions are included, or how the max_chars budget truncates the listing — a meaningful omission for a tool with a response-size parameter.

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 sentence that front-loads the verb and resource, then parenthetically enumerates the document categories. Every clause earns its place and there is no filler.

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 read-only listing tool with fully described parameters and no output schema, the description covers what the tool returns at a category level and confirms link usability via absolute URLs. Only minor gaps remain around result ordering and truncation behavior under max_chars.

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 100%, with bill, session, and max_chars each documented in the schema including formats and defaults, so the baseline of 3 applies. The description adds no parameter semantics beyond what the schema already states.

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 concrete verb ('List') and resource ('a bill's documents') and enumerates the document types returned (bill text versions, fiscal notes, committee reports, transmittal letters), so an agent can distinguish it from read_bill_text or get_fiscal_note which fetch single artifacts. It stops short of explicitly naming which sibling to use for a single document, keeping it at 4 rather than 5.

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 implied: reach for this when you need the set of documents attached to a bill, with the note that URLs are absolute so they can be followed directly. There is no explicit when-not guidance and no mention of the sibling tools that return a specific document's content, leaving the routing decision to inference.

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