Skip to main content
Glama
Sign In
Washington State Legislature MCP Server

Washington State Legislature MCP Server

by awalcutt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_bill_documents

Retrieve Washington State bill documents, including bill text, amendments, and reports, with links to HTML and PDF versions.

Instructions

Retrieve bill documents including bill text and amendments.

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) document_type: Filter by type - "bill", "amendment", "report" (optional)

Returns: Dict containing document metadata with links to HTML and PDF versions

Note: This tool returns metadata about available documents. To get the actual content of a bill in AI-friendly format, use the get_bill_content tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bill_number": "<bill_number>"
    },
    "name": "get_bill_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
bill_numberYes
bienniumNo
document_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that it returns metadata with links to HTML and PDF, and explains the document_type filter. However, it does not mention error handling or behavior for missing bills, but is otherwise clear.

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?

Two well-structured paragraphs with clear sections (summary, Args, Returns, Note). Every sentence adds value; no fluff. Front-loaded with purpose.

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?

Given the existence of an output schema, the description adequately explains parameters and return type. Covers purpose, parameters, and usage note. No missing critical information for a metadata retrieval 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?

With 0% schema description coverage, the description adds critical meaning: explains bill_number format (e.g., 1234 for HB1234), biennium format and default, and document_type allowed values ('bill', 'amendment', 'report'). Fully compensates for schema gaps.

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?

Description clearly states 'Retrieve bill documents including bill text and amendments' with a specific verb and resource. It distinguishes from sibling tool get_bill_content by noting that this tool returns metadata, not actual content.

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?

Provides explicit guidance: 'To get the actual content of a bill in AI-friendly format, use the get_bill_content tool.' This tells the agent when not to use this tool and gives an alternative.

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

Deploy Server

Other Tools