Skip to main content
Glama

Wa Bill Votes

wa_bill_votes
Read-onlyIdempotent

Get the recorded FLOOR ROLL-CALL VOTES on a Washington State legislative bill, chamber, motion ("3rd Reading & Final Passage"), date, and yea/nay/absent/excused counts with the voting legislators named in each category. Most recent vote first. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "how did the House vote on HB 1002", "did SB 5016 pass the Senate". Voice votes and committee-only votes are not recorded here. 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": {
      "bill": "HB 1002"
    },
    "name": "wa_bill_votes"
  }
}

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.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the description only needs to add context — and it does: 'Most recent vote first' ordering, the upstream source ('Reads directly from the Washington State Legislature's own bill-tracking service'), and 'Keyless' (no auth required). The one gap is nothing about volume or response size for a bill with many votes.

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?

The core capability is front-loaded in the first clause and the exclusions and sourcing follow logically; every sentence carries information. The all-caps emphasis and the two quoted example queries are slightly noisy but directly useful for matching user phrasing.

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 carries the burden of describing the return shape, and it does so concretely (chamber, motion, date, vote tallies, named legislators per category, most-recent-first ordering). It also covers the two exclusions an agent would otherwise miscall on and notes the keyless access model.

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%, with both `bill` (prefix-optional formats) and `biennium` (format examples, omit-for-current) fully documented, so the baseline is 3. The description's mention of 'chamber, motion, date' describes returned fields rather than inputs and could momentarily suggest filter parameters that do not exist.

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: 'Get the recorded FLOOR ROLL-CALL VOTES on a Washington State legislative bill', and enumerates the returned facets (chamber, motion, date, yea/nay/absent/excused counts, named legislators). This is clearly distinct from sibling tools like wa_bill_status or wa_bill_amendments, which cover status and text rather than roll-call records.

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 explicit when-to-use examples ('how did the House vote on HB 1002', 'did SB 5016 pass the Senate') and a clear when-not ('Voice votes and committee-only votes are not recorded here'). It stops short of naming a sibling to redirect to when the data is absent, so the routing half of the guidance is left implicit.

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.