West Virginia Rules

Search Rules

search_rules

Read-onlyIdempotent

Search West Virginia administrative rules (Code of State Rules) -- the agency regulations that implement WV statutes, e.g. Board of Medicine physician-assistant supervision, nursing practice, professional-licensing requirements. Filter by agency (e.g. "Medicine", "Registered Nurses, WV Board of"), title-series (e.g. "11-01B"), rule-name words, authorizing WV Code citation (e.g. "30-3E-3"), or full text of the rule documents. At least one filter is required. Returns counts by status first, then matching rule versions (active rules first). Use for "what does West Virginia require for X" when the answer is an agency rule rather than a statute; pair with wv_code_section for the statute and read_rule_text for the rule text.

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": 10,
      "status": "Active Only",
      "full_text": "physician assistant"
    },
    "name": "search_rules"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Rule versions to return (default 25, max 100). Counts always cover every match.
`agency`	No	Agency name as the register lists it, e.g. "Medicine", "Osteopathic Medicine", "Registered Nurses, WV Board of", "Physical Therapy".
`status`	No	Restrict by rule status. Omit for all versions (history included).
`authority`	No	Authorizing WV Code citation, e.g. "30-3E-3".
`full_text`	No	Words to find inside the rule documents, e.g. "collaborative agreement".
`rule_name`	No	Words in the rule title, e.g. "physician assistants".
`title_series`	No	Rule family, e.g. "11-01B" (title 11, series 01B = Board of Medicine physician assistants).
`full_text_mode`	No	any = any of the words (default); literal = exact phrase.

Output Schema

Name	Required	Description	Default
`next`	No
`rules`	No
`source`	No
`matches`	No
`returned`	No
`by_agency`	No
`by_status`	No
`data_as_of`	No
`filters_tried`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), lowering the bar. The description still adds real behavioral context: the mandatory 'at least one filter' constraint and the return ordering ('counts by status first, then matching rule versions, active rules first'). It stops short of noting pagination or truncation behavior, so not a full 5.

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-loads the resource and scope, then the filter list, then usage routing — a logical order. Slightly dense with repeated examples, but every sentence carries information and nothing is wasted.

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 an output schema present, the description needn't detail return values, yet it still summarizes the count-then-versions ordering. Combined with the usage routing and filter constraint, an agent has 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%, so the baseline is 3, but the description adds a semantic the schema omits: at least one filter must be supplied (required params count is 0, so this constraint only lives in prose). The enumerated filter categories (agency, title-series, rule-name words, authorizing citation, full text) mirror the schema.

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 West Virginia administrative rules (Code of State Rules)') and disambiguates from statutory search by explaining these are agency regulations implementing WV statutes, with concrete examples. An agent can distinguish it from siblings like get_rule and read_rule_text without opening a schema.

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?

Explicitly frames the use case ('what does West Virginia require for X' when the answer is an agency rule rather than a statute) and names the complementary tools (wv_code_section for statutes, read_rule_text for rule text). It also states the hard constraint that at least one filter is required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All West Virginia Rules tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.