Skip to main content
Glama

Wa Wac Search

wa_wac_search
Read-onlyIdempotent

Search the FULL TEXT of the Washington Administrative Code (WAC) by topic or keyword, "workplace safety bulletin board", "security deposit", "septic system permit", "cannabis retailer". Calls the Washington State Legislature's own full-text search index of every WAC section (it matches rule TEXT, not just captions), returns matching citations with captions, highlighted snippets and the index-wide match count. Optionally restrict to a title or chapter with cite_prefix ("296" for L&I, "458-20" for Revenue excise-tax rules). Call wa_wac_section with a citation for the full text and history. 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": {
      "limit": 5,
      "query": "safety bulletin board"
    },
    "name": "wa_wac_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 25.
queryYesTopic or keywords, e.g. "safety bulletin board" or "landlord deposit". Plain words; the index is Elasticsearch-style (all terms, stemmed).
cite_prefixNoOptional WAC title or chapter to restrict results to, e.g. "296" or "296-800".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real value beyond them: it explains the search is backed by the Legislature's own Elasticsearch-style index over rule text, describes the return shape (citations, captions, highlighted snippets, index-wide match count), and notes the tool is keyless.

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?

One dense paragraph, front-loaded with the core purpose and then the differentiating detail. The four quoted keyword examples early on are somewhat redundant against the schema's own example, but nothing is padded or circular.

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 three simple parameters, full schema coverage, and no output schema, the description carries the return-value burden itself and does so: it names what comes back (citations, captions, snippets, match count) and what is returned when nothing is narrowed versus prefixed. Nothing an agent needs to invoke it correctly is 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 schema already documents query, limit and cite_prefix in detail. The description contributes the agency mapping for cite_prefix ('296' for L&I, '458-20' for Revenue excise-tax rules), which is not in the schema, though its quoted query examples largely duplicate the schema's example.

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 ('Search the FULL TEXT of the Washington Administrative Code') and immediately scopes it: full-text index matching rule TEXT, not just captions. It is clearly distinguishable from wa_wac_section, which is named as the full-text/history retriever once you have a citation.

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 the trigger (topic or keyword search when you don't yet have a citation) and explicitly routes the alternative: 'Call wa_wac_section with a citation for the full text and history.' It also shows how to narrow scope with cite_prefix, so the agent knows both when to use and how to constrain this tool.

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.