Skip to main content
Glama

get_bill

Read-only

Retrieve a Utah bill's metadata—title, sponsors, status, summaries, subjects, affected code sections, and versions—without bill text; use the bill-text loader for full text.

Instructions

Get a bill's metadata: title, sponsors, status, and (standard/full) its summary, subjects, affected code sections, versions. Does not include bill text - use load_bill for that.

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

Input Schema

NameRequiredDescriptionDefault
billYesBill number, e.g. 'HB 1', 'SB42', 'HJR 3'.
detailNobrief = one line per item; standard adds summaries; full adds everything.standard
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

A4.4/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 safety is covered. The description adds real behavioral context by naming the exact content envelope and the deliberate omission of bill text, which prevents a wasted call. It stops short of describing response shape or pagination/truncation behavior (relevant given the max_chars 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?

Two tight sentences: the first front-loads what is returned, the second front-loads the exclusion and the alternative. No filler, no restatement of the title, and no redundancy with the schema.

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 metadata tool with no output schema, the description covers the returned fields and the key exclusion well enough to call it correctly. The remaining gap is behavioral detail around truncation given max_chars, which the description never acknowledges.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by mapping the detail levels to concrete content ('(standard/full) its summary, subjects, affected code sections, versions'), which tells the agent what it gains by raising detail. It says nothing about the session or max_chars parameters beyond what the schema already documents.

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?

The description gives a specific verb and resource ('Get a bill's metadata') and enumerates exactly what is returned (title, sponsors, status, summary, subjects, affected code sections, versions). It also explicitly bounds the tool by excluding bill text and pointing to load_bill, so an agent can distinguish it from siblings without opening a schema.

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 clearly states the primary exclusion and the alternative ('Does not include bill text - use load_bill for that'), which is the most likely routing confusion. It does not offer guidance on when to prefer get_bill_history, get_bill_documents, or get_fiscal_note, leaving some selection decisions to inference.

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