Skip to main content
Glama

load_bill

Read-only

Load a bill's full text into server-side working memory and return only its table of contents. Then read sections piece by piece or search them without pulling the whole bill into context.

Instructions

Load a bill's full text into the server's working memory and return only a table of contents (section ids, headings, sizes). The text stays server-side: read it piece by piece with read_bill_text or search it with find_in_bill. Up to 10 bills stay loaded.

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

Input Schema

NameRequiredDescriptionDefault
billYesBill number, e.g. 'HB 1', 'SB42', 'HJR 3'.
refreshNoForce a re-download even if unchanged.
sessionNoSession, e.g. '2026', '2026GS', '2025S1'. Omit for the current general session.
versionNoText version, e.g. 'Introduced', 'Enrolled', '1st Sub'. Default: enrolled, else latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/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; the description adds the non-obvious behavior that full text persists server-side rather than being returned. It does not explain eviction behavior when the 10-bill cap is exceeded. The load-into-working-memory framing is a server-side cache side effect rather than a contradiction of readOnlyHint.

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?

Three sentences, front-loaded with the action and return shape, followed by the retrieval path and the capacity limit. No redundant restatement of the tool name or schema fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing the return value and does so concretely ("section ids, headings, sizes"). Combined with the follow-on tool routing and the loaded-bill cap, an agent has everything needed to call it correctly and use the result.

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 the baseline applies: bill, refresh, session, and version are all documented in the schema, including defaults and examples. The description adds no parameter-level meaning beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ("Load a bill's full text") plus explicit scope of what is returned ("only a table of contents (section ids, headings, sizes)"). This clearly separates it from read_bill_text and find_in_bill, which operate on already-loaded text.

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

Usage Guidelines5/5

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

Names the two follow-on alternatives explicitly ("read it piece by piece with read_bill_text or search it with find_in_bill"), which tells the agent exactly when this tool is the entry point versus a follow-up. It also states the operational limit ("Up to 10 bills stay loaded"), which affects when to unload or avoid loading more.

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