West Virginia Rules

Get Rule

get_rule

Read-onlyIdempotent

Get one West Virginia administrative rule family by title-series (e.g. "11-01B"): every version ever filed with its effective date, status (Active, Historical, Emergency), authorizing statute, and the filing history (modified/agency-approved/legislative-approval filings) with document ids that read_rule_text can open. Use after search_rules to see the current rule and what superseded it.

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": {
      "title_series": "11-01B"
    },
    "name": "get_rule"
  }
}

Input Schema

Name	Required	Description	Default
`document`	No	Optionally, a rule version document number from search_rules to list that version's filings instead.
`title_series`	No	Rule family, e.g. "11-01B".

Output Schema

Name	Required	Description	Default
`next`	No
`agency`	No
`source`	No
`data_as_of`	No
`all_versions`	No
`title_series`	No
`version_count`	No
`current_version`	No
`filings_for_current_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior3/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 adds return-shape context (status values, filing types, document ids), but since an output schema exists this is largely redundant rather than new behavioral disclosure. No auth, rate-limit, or pagination behavior is described.

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?

Two sentences, front-loaded with the primary action and followed by usage guidance; nothing is wasted. The first sentence is dense with enumeration but each element (statuses, statute, filing history) is load-bearing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be re-explained, yet the description covers purpose, returns, and the sibling relationship well. The one minor gap is that both parameters are optional and the description does not say what happens if neither title_series nor document is supplied.

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%, so the schema already documents both parameters. The description reinforces title-series with the '11-01B' example and hints that document ids feed read_rule_text, but adds no syntax or constraint detail beyond the schema. Baseline 3 is correct when the schema carries the parameter burden.

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 one West Virginia administrative rule family by title-series') and enumerates exactly what is returned: versions, effective dates, status values, authorizing statute, and filing history. It also distinguishes itself from siblings by naming read_rule_text (which opens the document ids) and search_rules, so an agent can tell it apart without opening any schema.

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?

Explicitly routes usage: 'Use after search_rules to see the current rule and what superseded it,' which names the alternative and the workflow ordering. It does not state a when-not-to-use case, so it stops short of full alternative routing, but the context is clear.

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.