Skip to main content
Glama

read_bill_text

Read-only

Reads a section or paged slice of a bill's text, loading it as needed; amendments appear as [+inserted+] and [-deleted-], with offset/next_offset for paging.

Instructions

Read a slice of a bill's text (loads the bill if needed). Amendments are marked [+inserted+] and [-deleted-]. Page with offset/next_offset.

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

Input Schema

NameRequiredDescriptionDefault
billYesBill number, e.g. 'HB 1', 'SB42', 'HJR 3'.
offsetNoStart position for paging; use next_offset from a prior call.
sectionNoSection id from load_bill's table of contents (e.g. '53F-2-301', 'S5', 'intro'). Omit to page through the whole bill.
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.8/5.0
Behavior4/5

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

Beyond the readOnly and openWorld annotations, the description discloses that the tool may load the bill and explains amendment markup conventions ([+inserted+] and [-deleted-]). It also mentions paging, adding useful behavioral context, though it does not discuss truncation or error behavior.

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?

The description is concise and front-loaded, stating the core action first, then amendment markup, then paging. Every sentence contributes directly to correct invocation.

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 text-paging tool with a fully described schema and no output schema, the description covers the main behavior, loading side effect, amendment formatting, and paging. It could be slightly more complete by clarifying the return shape or how next_offset appears in responses, but it is largely sufficient.

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%, so the schema already documents all five parameters in detail. The description only adds a brief paging hint about offset/next_offset and does not add meaningful semantics for section, session, or max_chars beyond what the schema provides.

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 and resource: "Read a slice of a bill's text." It also notes that the bill is loaded if needed, which partially distinguishes it from tools like load_bill or get_bill, but it does not explicitly contrast itself with find_in_bill or get_bill.

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 implies usage for reading bill text and paging with offset/next_offset, but it does not explicitly state when to use this tool instead of alternatives such as get_bill, find_in_bill, or load_bill. Guidance is present but mostly mechanical.

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