Skip to main content
Glama

Wa Session Bills

wa_session_bills
Read-onlyIdempotent

List Washington State legislative bills for a BIENNIUM filtered by procedural status: "introduced" (every bill filed, default), "passed_house", "passed_senate", "passed_legislature", "signed" (by the Governor), "vetoed", or "partial_veto" (the last three require agency: "House" or "Senate", the chamber of origin). Returns aggregate counts (by chamber, by type, active count) first, then a page of bare bill records (id, type, chamber, active), call wa_bill_status on an id for its description. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "how many bills passed the Legislature in 2025-26", "what did the Governor sign from the House in 2025-26". Keyless.

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": {
      "limit": 5,
      "status": "passed_legislature",
      "biennium": "2025-26"
    },
    "name": "wa_session_bills"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax records to return, default 15, max 50.
agencyNoChamber of origin, "House" or "Senate", required for status signed/vetoed/partial_veto.
offsetNoPagination offset into the full result set, default 0.
statusNoOne of: introduced (default), passed_house, passed_senate, passed_legislature, signed, vetoed, partial_veto.
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. Changed1 schema field changed
    • changedInput schema / properties / agency / description
      Previous value: -"Chamber of origin, \"House\" or \"Senate\" — required for status signed/vetoed/partial_veto."New value: +"Chamber of origin, \"House\" or \"Senate\", required for status signed/vetoed/partial_veto."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Adds meaningful behavior beyond the annotations: the response returns aggregate counts (by chamber, by type, active count) before a page of 'bare' bill records, so an agent knows it must call wa_bill_status to get descriptions. It also discloses 'Keyless' operation, which matters for auth planning, though it says nothing about rate limits or upstream source freshness beyond naming the Legislature's bill-tracking service.

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?

Front-loads the verb, resource, and filter axis in the first clause, then the status enumeration, then output shape, then the sibling hand-off and cost/auth note. Dense but every clause carries information an agent needs; no filler or repeated schema text.

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?

All five parameters are optional and documented at 100% coverage, and the description supplies the two things the schema cannot: the aggregate-then-page return structure and the fact that records are bare and need wa_bill_status for detail. For a keyless read-only listing tool with no output schema, nothing material is missing.

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 goes further by explaining what each status actually means in legislative terms and restating that the last three statuses require the agency chamber of origin. It does not add anything about limit/offset semantics beyond the schema, which caps the score.

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 and resource ('List Washington State legislative bills'), the scoping dimension (biennium + procedural status), and enumerates every status value with plain-language glosses ('signed' by the Governor, 'partial_veto'). It also explicitly distinguishes itself from wa_bill_status, which returns the description of a single bill, so an agent can separate the two 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?

Gives concrete selection scenarios ('how many bills passed the Legislature in 2025-26', 'what did the Governor sign from the House in 2025-26') and names the follow-up tool (wa_bill_status on an id) for detail. It never states when not to use it, e.g. that in-session bills or single-bill lookups belong elsewhere, so it falls short of the full when/when-not/alternatives bar.

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.