Skip to main content
Glama

list_passed_bills

Read-only

Retrieve bills that passed the Utah Legislature since 2016, including governor action, with filters for session and governor action plus paging.

Instructions

Bills that passed the Legislature in a session (2016+), with governor action.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (1-50).
offsetNoStart position for paging; use next_offset from a prior call.
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.
governor_actionNoFilter by governor action code, e.g. 'GSIGN', 'GOVLVETO'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 safety is covered. The description adds the 2016+ coverage floor, but says nothing about default page size behavior, whether governor_action-less bills are included, or whether 'passed' includes vetoed bills, despite the filter existing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and every clause (session, 2016+, governor action) carries information. It is fragmentary rather than structured, but nothing is wasted.

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

Completeness3/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 does not say what a returned bill record contains or how results are ordered, which matters for a list tool with paging. Scope and temporal bounds are stated, so it is adequate but not complete.

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 all five parameters including session formats and governor action codes are already documented. The description only lends slight extra meaning by tying session and governor action to the passed-bill concept; 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 names a specific resource and scope: bills that passed the Legislature, per session, from 2016 onward, annotated with governor action. That distinguishes it from generic siblings like list_bills or search_bills by implication, though it never names an alternative.

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 only implied: an agent can infer it is for enumerating enacted bills, and the '2016+' clause hints at a coverage floor. There is no explicit when-to-use/when-not statement or comparison to search_bills or list_bills for broader queries.

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