West Virginia Rules

Read Rule Text

read_rule_text

Read-onlyIdempotent

Read the text of a West Virginia administrative rule filing (the rule as filed). Takes a filing document id from get_rule. Returns the text in pages of characters with total length so long rules can be read in sequence via offset. Filings described "Modified File" are redlines (struck and inserted text both appear, e.g. old and new section numbers side by side); the "Agency Approved" and "Valid" filings are cleaner. Use to quote the exact supervision, scope-of-practice, or licensing requirement.

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": {
      "find": "supervis",
      "doc_id": 59557,
      "max_chars": 3000
    },
    "name": "read_rule_text"
  }
}

Input Schema

Name	Required	Description
`find`	No	Optional: return the passages around this phrase instead of a linear page.
`doc_id`	Yes	Filing document id from get_rule, e.g. 59557.
`offset`	No	Character offset to start from (default 0).
`max_chars`	No	Characters to return (default 20000, max 40000).

Output Schema

Name	Required	Description	Default
`find`	No
`pages`	No
`doc_id`	No
`source`	No
`matches`	No
`passages`	No
`warnings`	No
`total_chars`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already establish the safe, idempotent, read-only profile, and the description goes further by disclosing the pagination model (characters per page with total length, sequenced via offset) and a non-obvious behavioral trait: "Modified File" filings are redlines with struck and inserted text side by side, while "Agency Approved" and "Valid" are cleaner. That redline caveat materially affects how an agent interprets the returned text and is not derivable from any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, none wasted: purpose and input source first, pagination model second, filing-quality caveat and use case last. Every clause carries information an agent needs.

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, return formatting need not be re-explained, and the annotations cover the safety profile. The description fills the remaining gaps — where doc_id comes from, how to page through long rules, and how redline filings differ — leaving nothing needed to invoke it correctly.

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 all four parameters are already documented in the schema. The description reinforces offset's purpose (reading long rules in sequence) and doc_id's origin, but adds little syntax or format meaning beyond what the schema provides. Baseline 3 is appropriate.

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 ("Read the text of a West Virginia administrative rule filing") and pins the scope to the rule as filed. It also implicitly separates itself from siblings by naming get_rule as the source of the doc_id, so an agent knows this tool reads rather than retrieves the filing.

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?

Gives a clear use case ("quote the exact supervision, scope-of-practice, or licensing requirement") and the dependency (doc_id from get_rule). It does not name a when-not or contrast directly with search_rules/search_within, so it stops short of the top band.

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.