Skip to main content
Glama

list_bills

Read-only

Lists numbered bills for a legislative session with last-update times; supports sorting, paging, bill-type/session filters, and updated-since queries, with bill details available via other tools.

Instructions

List numbered bills in a session with last-update times (titles included when the search index has been built). Use get_bill or search_bills for details.

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

Input Schema

NameRequiredDescriptionDefault
sortNo'recent' = most recently updated first.number
limitNoMax items to return (1-50).
offsetNoStart position for paging; use next_offset from a prior call.
prefixNoBill type: HB, SB, HJR, SJR, HCR, SCR, HR, SR.
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.
updated_sinceNoISO date/time, e.g. '2026-02-15'. Only bills updated on/after.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a genuinely useful behavioral condition beyond that: titles appear only when the search index has been built, which tells the agent why output may vary between calls.

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?

Two sentences, zero waste, with the core purpose front-loaded and the alternative-tool routing following it. The parenthetical caveat is compact and earns its place.

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 7-parameter read-only listing tool with no output schema, the description covers the essential return shape (numbers, update times, conditional titles) and the main alternative. It says nothing about how max_chars truncates responses, but the schema's documented paging and budget parameters largely fill that gap.

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 sorting, paging, prefix, session, char budget, and the updated_since filter are all fully documented in the schema itself. The description's references to sessions and update times merely echo those parameters rather than adding format or behavior detail, so baseline 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 description states a specific verb and resource ('List numbered bills in a session') plus the fields returned (last-update times, conditional titles), and it names two sibling tools so an agent can route away when details are needed. It does not differentiate from the other list_* siblings, which keeps it short of a 5.

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

Usage Guidelines4/5

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

It explicitly routes the agent to get_bill or search_bills when per-bill details are wanted, which is clear when-to-use guidance. It offers no exclusions relative to the other list variants, but the condition it does state is unambiguous.

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