wa_session_bills

Pack: washington-code · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/wa_session_bills for the schema, then POST the same URL with its arguments for the data.

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.

Parameters

Example call

Arguments

{
  "biennium": "2025-26",
  "status": "passed_legislature",
  "limit": 5
}

curl

curl -X POST https://gateway.pipeworx.io/washington-code/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"wa_session_bills","arguments":{"biennium":"2025-26","status":"passed_legislature","limit":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('wa_session_bills', {
  "biennium": "2025-26",
  "status": "passed_legislature",
  "limit": 5
});

More examples

{
  "biennium": "2025-26",
  "status": "signed",
  "agency": "House",
  "limit": 3
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

{
  "mcpServers": {
    "washington-code": {
      "url": "https://gateway.pipeworx.io/washington-code/mcp"
    }
  }
}

See Getting Started for client-specific install steps.