Skip to main content
Glama

Wa Bill Amendments

wa_bill_amendments
Read-onlyIdempotent

List the AMENDMENTS proposed to a Washington State legislative bill, amendment name/drafting number, sponsor (member or committee), type (floor/committee), description, floor action (ADOPTED/FAILED/WITHDRAWN) and date, with links to the amendment text. Returns the most recent amendment first and a count by floor action. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "what amendments have been offered to HB 1002", "was the striker amendment adopted on SB 5016". A bill with no amendments on file returns an empty list, not an error. Keyless. For the bill's overall status use wa_bill_status.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bill": "1002",
      "biennium": "2023-24"
    },
    "name": "wa_bill_amendments"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYesBill number, with or without prefix: "HB 1002", "SB 5016", or bare "1002".
bienniumNoWashington biennium, e.g. "2025-26" or a year like "2026". Omit for the current biennium.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses ordering ('most recent amendment first'), an aggregate count by floor action, source authority, keyless access, and empty-list semantics. These details materially help an agent interpret results and avoid treating a zero-amendment bill as a failure.

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 information-dense and front-loaded: it states what is listed, what fields are returned, ordering, source, examples, empty-list handling, and the sibling alternative. Despite the long first sentence, every clause adds useful selection or interpretation context.

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?

There is no output schema, so the description carries the burden of explaining returned fields, ordering, and the floor-action count, all of which it does. It also covers the empty-result case and source behavior, leaving no major gap for a read-only bill-amendment tool.

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 schema already documents bill number formats and biennium defaults. The description does not add meaningful parameter syntax or behavior beyond what the schema provides, making the baseline 3 appropriate.

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 uses a specific verb, 'List', and a precise resource, 'AMENDMENTS proposed to a Washington State legislative bill'. It enumerates the returned fields and explicitly distinguishes itself from wa_bill_status for overall bill status, so an agent can identify its role without opening the schema.

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?

It gives concrete usage examples ('what amendments have been offered to HB 1002', 'was the striker amendment adopted on SB 5016') and names the alternative tool for overall status. It also clarifies that an empty list is not an error, which prevents misinterpreting a valid no-amendment result.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.