Skip to main content
Glama

Wa Wac Archived Section

wa_wac_archived_section
Read-onlyIdempotent

Get the text of a Washington Administrative Code (WAC) section AS IT STOOD at the end of a PAST YEAR, from the Legislature's annual WAC archive. Year-end snapshots with full text for 2019 onward (e.g. "WAC 296-800-110 in 2020"); 2004-2018 are PDF-only and the tool returns the chapter PDF link for 2016-2018 and the archive directory for earlier years rather than text. Returns the archived text, caption and the history line as printed that year, so you can diff it against wa_wac_section (current). Keyless. Use for "what did WAC 314-55-010 say in 2021", or to check which version of a rule applied on a date.

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": {
      "year": 2020,
      "section": "296-800-110"
    },
    "name": "wa_wac_archived_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesArchive year, 2004-last year. Full text for 2019 onward; PDF-only before that.
sectionYesWAC section citation, e.g. "296-800-110".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / year / description
      Previous value: -"Archive year, 2004–last year. Full text for 2019 onward; PDF-only before that."New value: +"Archive year, 2004-last year. Full text for 2019 onward; PDF-only before that."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses real behavioral detail: keyless access, full text only from 2019 onward, PDF-link fallback for 2016-2018 and archive-directory fallback for earlier years, and what is actually returned (archived text, caption, history line as printed). This is exactly the kind of coverage-dependent degradation an agent needs before calling.

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?

Front-loaded with the core operation, then caveats, then use cases; almost every clause carries information. The opening sentence is long and packs fallback rules mid-paragraph, which slightly hurts scannability but wastes little.

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?

No output schema exists, so the description carries the return-value burden and does so fully (text, caption, history line, or PDF/directory link depending on year), plus access and fallback semantics. Nothing an agent needs to call this correctly appears missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the valid year window (2004-last year) and the year-dependent output format, plus the section citation format. It could still be sharper on how year/section interact when the section doesn't exist that year.

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 (get the text) and resource (WAC section as it stood in a past year from the Legislature's annual archive), and explicitly contrasts with wa_wac_section (current), so an agent can distinguish the two without opening schemas.

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 concrete triggering questions ("what did WAC 314-55-010 say in 2021", checking which version applied on a date) and names the current-version sibling for the alternative case. It stops short of stating when NOT to use it (e.g. for the current text), though the wa_wac_section pointer implies that exclusion.

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.