Skip to main content
Glama

Wa Rcw Section

wa_rcw_section
Read-onlyIdempotent

Get the FULL TEXT of a section of the Revised Code of Washington (RCW), Washington state STATUTES, by citation. "RCW 9A.32.030" is first degree murder. Returns the statutory text and its heading. Keyless. Use for "what does RCW 46.61.502 say", "text of RCW 49.60.180", or to check a Washington statute a case relies on. For agency RULES (Washington Administrative Code, citations like "WAC 296-800-110") use wa_wac_section instead.

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": "9A.32.030"
    },
    "name": "wa_rcw_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesRCW citation, e.g. "9A.32.030" or "46.61.502". Title.chapter.section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely new context beyond that: it is keyless (no auth setup needed) and it returns the statutory text plus its heading. It does not discuss failure behavior for invalid or nonexistent citations, which is the main remaining gap.

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 action and scope, then examples, then the sibling routing. Slightly repetitive across the three example phrasings, but each sentence still serves routing or disambiguation.

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 single-parameter, keyless lookup with no output schema, the description covers what goes in (citation format), what comes out (statutory text and heading), and when to pick the sibling instead. Nothing an agent needs in order to call it correctly is missing.

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 itself documents the Title.chapter.section format with examples. The description reinforces the citation shape through a worked example but adds no new syntax rules, such as whether an "RCW " prefix is accepted. Baseline 3 is appropriate when the schema carries the parameter detail.

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 FULL TEXT of a section of the Revised Code of Washington), clarifies the resource type as state STATUTES rather than rules, and gives a concrete citation example. An agent can immediately distinguish this from the WAC siblings.

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 explicit use cases ("what does RCW 46.61.502 say", checking a statute a case relies on) and an explicit exclusion with the correct alternative: use wa_wac_section for WAC citations like "WAC 296-800-110". The routing condition is unambiguous.

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.