Skip to main content
Glama
Sign In

West Virginia Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Wv Code Section

wv_code_section
Read-onlyIdempotent

Get the FULL TEXT of a section of the West Virginia Code — West Virginia state law — by citation. "W. Va. Code 61-2-1" is first degree murder. Returns the statutory text. Keyless. Use for "what does West Virginia Code 61-2-1 say" or to check a WV statute a case relies on.

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": "61-2-1"
    },
    "name": "wv_code_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "61-2-1" (murder) or "17C-5-2" (DUI). Chapter-article-section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive hints. The description adds 'Keyless' (an authentication detail) and confirms 'Returns the statutory text,' which is useful beyond the annotation metadata. It does not mention rate limits or data currency, but the safety profile is already covered.

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, front-loaded with the core purpose, then an example and use cases. Every sentence earns its place; there is no filler or redundancy. The structure is compact and immediately scannable.

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?

For a simple one-parameter lookup tool, the description covers the resource, citation format, what it returns, and typical usage. Since there is no output schema, explicitly stating 'Returns the statutory text' is valuable. Minor details like legislative version or currency are absent, but not essential for an agent to select and invoke this tool 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?

The input schema fully documents the single 'section' parameter with examples and format explanation (100% coverage). The description reinforces the citation format with additional examples, but adds no meaning beyond what the schema already provides, so the baseline 3 applies.

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?

The description states a specific verb ('Get the FULL TEXT') and resource ('a section of the West Virginia Code'), with a clear citation format and an illustrative example ('61-2-1' is first degree murder). It fully distinguishes the tool's function from the sibling list, none of which overlap with statutory text retrieval.

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?

Explicit use cases are given: 'Use for "what does West Virginia Code 61-2-1 say" or to check a WV statute a case relies on.' It does not enumerate when-not-to-use or alternatives, but sibling tools are unrelated, so this is clear, actionable context rather than a gap.

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

All West Virginia Code toolsInspect
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.

Resources