Skip to main content
Glama

Wa Wac Section

wa_wac_section
Read-onlyIdempotent

Get the CURRENT FULL TEXT of a section of the Washington Administrative Code (WAC), Washington state agency RULES / regulations, by citation. "WAC 296-800-110" is L&I's safe-workplace summary; "458-20-178" is the Department of Revenue use-tax rule. Returns the rule text, its caption, the statutory-authority history (every WSR filing that amended it, with filed/effective dates) and the RCW sections the agency cited as authority. A repealed or nonexistent section is reported as found:false (the site redirects it). Keyless. Use for "what does WAC 296-800-110 say", "text of WAC 388-76-10000", or to check a Washington regulation an agency decision cites. For STATUTES (RCW) use wa_rcw_section; for past years use wa_wac_archived_section; to search by topic use wa_wac_search.

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

Input Schema

NameRequiredDescriptionDefault
sectionYesWAC citation, title-chapter-section, e.g. "296-800-110" or "WAC 458-20-178". Chapter and title parts may carry a letter suffix ("296-14A-100", "132C-120-010").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the return payload (rule text, caption, WSR amendment history with filed/effective dates, cited RCW authority), the failure mode for repealed or nonexistent sections (found:false due to a site redirect), and that no key is required. That is substantive behavior the annotations cannot convey.

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 verb and resource, then examples, then routing rules — no filler sentences. It is dense and slightly long for a single-parameter lookup, but every clause (found:false, keyless, alternatives) carries information.

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?

For a simple one-parameter retrieval tool with no output schema, the description covers input format, return contents, not-found handling, and sibling routing — everything needed to call it correctly.

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% and already documents the citation format, so the baseline applies; the description adds value by showing both bare ('296-800-110') and prefixed ('WAC 458-20-178') citation forms and noting letter suffixes in title/chapter parts, which reduces malformed-input risk.

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 and resource — 'Get the CURRENT FULL TEXT of a section of the Washington Administrative Code' — with concrete example citations and an explicit note that it is agency rules, not statutes. It distinguishes itself from wa_rcw_section and wa_wac_archived_section by name.

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?

Gives concrete when-to-use triggers ('what does WAC 296-800-110 say', 'check a Washington regulation an agency decision cites') and routes the alternatives explicitly: wa_rcw_section for statutes, wa_wac_archived_section for past years, wa_wac_search for topics.

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.