Skip to main content
Glama
awalcutt

Washington State Legislature MCP Server

by awalcutt

get_bill_content

Retrieve the structured content of a Washington State bill in XML, HTML, or PDF format. Specify the bill number and optional chamber or biennium to access the full bill document.

Instructions

Retrieve the content of a bill in an AI-friendly format.

This tool fetches the actual content of a bill document, defaulting to XML format which is most suitable for AI processing due to its structured nature. It can also return HTML content or a link to the PDF version.

Args: bill_number: Bill number as an integer (e.g., 1234 for HB1234, 5678 for SB5678) biennium: Legislative biennium in format "YYYY-YY" (e.g., "2025-26") (optional, defaults to current) chamber: Chamber name - "House" or "Senate" (optional if bill_number is unique across chambers) bill_format: Document format - "xml" (default), "htm", or "pdf"

Returns: For XML and HTM formats: Dict containing the document content and metadata For PDF format: Dict containing the URL to access the PDF and metadata

Note: This tool complements the get_bill_documents tool, which provides metadata about available documents. This tool provides the actual content of the bill.

When citing bill content in responses, consider including a link to the PDF version
using the format: https://lawfilesext.leg.wa.gov/biennium/{biennium}/Pdf/Bills/{chamber}%20Bills/{bill_number}.pdf

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bill_numberYes
bienniumNo
chamberNo
bill_formatNoxml

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses default format, optional parameters, and behavior for different formats. Explains chamber optionality and includes example bill_number usage. No annotations present, so description carries full burden and meets it well.

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?

Well-structured with sections for args, returns, and notes. However, slightly verbose with details like PDF link format. Still effective and not overly long.

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?

Covers all aspects: purpose, parameters, returns, and citation guidance. Has output schema but description still adds value. No gaps identified.

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?

Despite 0% schema description coverage, the description provides clear, detailed explanations for each parameter: bill_number with example, biennium format, chamber as string, bill_format options. Adds significant meaning beyond schema.

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 states it retrieves bill content in AI-friendly format, specifies default XML format, and distinguishes from sibling get_bill_documents which provides metadata.

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?

Explicitly states when to use (need actual content) and when not (metadata via get_bill_documents). Also advises on citation and PDF link usage.

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