Skip to main content
Glama

Wa Wac Filings

wa_wac_filings
Read-onlyIdempotent

List the Washington State Register (WSR) rule-making FILINGS that affected a Washington Administrative Code (WAC) section or chapter, the amendment history as agency actions: WSR number, filing type (Permanent Rule, Proposal Original Notice, Emergency Rule, Expedited Rule Making, Preproposal Statement of Inquiry...), date filed, and a link to the filing text. Newest first. Use for "when was WAC 296-800-110 last amended", "is there a pending proposal to change chapter 458-20 WAC", or to trace a rule's rule-making record. 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": {
      "cite": "296-800-110"
    },
    "name": "wa_wac_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
citeYesWAC section ("296-800-110") or chapter ("296-800").

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?

The annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuinely new context: results are newest-first, the record types included, the shape of each filing entry, and 'Keyless' (no auth required). Pagination and result-size limits are the main omission.

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?

It is front-loaded with the core purpose and ordering, and every clause carries information. The parenthetical list of filing types plus the trailing '...' is slightly bulky, but it aids interpretation rather than padding.

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 one simple parameter, full schema coverage, and no output schema, the description supplies what's missing: the returned fields, sort order, and auth model. An agent has everything needed to call it and interpret the response.

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 coverage is 100% and the schema already documents the `cite` parameter with section and chapter examples. The description reinforces that either a section or chapter is accepted but adds no format or edge-case detail beyond the schema, so baseline 3 applies.

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 uses a specific verb and resource: list WSR rule-making filings affecting a WAC section or chapter, and it explicitly frames the result as amendment history. It also enumerates the returned fields (WSR number, filing type, date filed, link), so an agent can tell this apart from a tool that returns current section text.

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?

It gives three concrete use cases: finding when a section was last amended, checking for a pending proposal, and tracing rule-making records. It does not state when NOT to use it or name a sibling alternative, so it falls short of full routing guidance.

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.