Skip to main content
Glama

Wa Bill Status

wa_bill_status
Read-onlyIdempotent

Get the current status of a Washington State LEGISLATIVE BILL, its description, legal title, sponsor(s), introduced date, procedural history line and current status (e.g. "H Rules X", "Passed Legislature"), and companion bills in the other chamber. Reads directly from the Washington State Legislature's own bill-tracking service (not a third-party aggregator). Use for "what is the status of HB 1000", "who sponsored SB 5016", "is HB 1002 still active". Bill numbers reset each biennium (default: the current one), pass biennium for a past session. Keyless. For an amendment history use wa_bill_amendments; for floor votes use wa_bill_votes; for everything introduced in a session use wa_session_bills.

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": "HB 1002"
    },
    "name": "wa_bill_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYesBill number, with or without prefix: "HB 1000", "SB 5016", "2SHB 1000", or bare "1000".
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.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added value is provenance and access context: it reads the Legislature's own tracking service rather than an aggregator, and it is keyless. It does not discuss rate limits or failure behavior for unknown bills, keeping it just short of a 5.

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?

Front-loaded with purpose and return fields, then usage examples, then routing to siblings — a logical order with no filler. It is on the longer side, but nearly every clause carries information an agent needs.

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 compensates by enumerating the returned fields (status codes like 'H Rules X', sponsor, companion bills) and their source system. Combined with the biennium caveat, an agent has everything needed to call it correctly and interpret the result.

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 baseline would be 3, but the description adds real meaning beyond the schema: bill numbers reset each biennium, the biennium defaults to the current one, and a biennium must be passed for past sessions — semantics the schema field text only partially implies.

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?

States a specific verb+resource ('Get the current status of a Washington State LEGISLATIVE BILL') and enumerates exactly what is returned: description, legal title, sponsors, introduced date, procedural history, current status, companion bills. It also names the sibling tools for adjacent needs, so an agent can differentiate it without opening any 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?

Gives concrete trigger queries ('what is the status of HB 1000', 'who sponsored SB 5016'), names explicit alternatives and what selects them (wa_bill_amendments for amendment history, wa_bill_votes for floor votes, wa_session_bills for all introduced bills), and specifies the biennium rule for past sessions.

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.