Skip to main content
Glama
awalcutt

Washington State Legislature MCP Server

by awalcutt

find_legislator

Find legislators by biennium, chamber, or district to identify sponsors of legislation in Washington State.

Instructions

Find legislators (sponsors) for a specific biennium, optionally filtered by chamber and/or district.

Args: biennium: Legislative biennium in format "2025-26" (optional, defaults to current) chamber: Filter by chamber ("house" or "senate") (optional) district: Filter by legislative district number (optional)

Returns: Dict containing list of legislators matching the criteria

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bienniumNo
chamberNo
districtNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must cover behavior. It specifies return type (dict with list) but lacks details on pagination, errors, or side effects. Basic but not fully transparent.

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 very concise with a clear structure: main action, then bullet-pointed args, then return info. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the essential purpose and parameters but could be more precise (e.g., specifying chamber values as literal 'house' or 'senate', and district as integer). Still adequate for a simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description adds clear meaning for all three parameters: biennium (default current), chamber (house/senate), district (number). This fully compensates for the schema gap.

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 clearly states it finds legislators (sponsors) for a given biennium with optional filters, distinguishing it from sibling tools that handle bills or committee meetings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the parameters and defaults but does not explicitly guide when to use this tool versus alternatives like search_bills. No when-not-to-use or alternative mentions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/awalcutt/wa-leg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server