Skip to main content
Glama

Wy Statute

wy_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Wyoming Statutes (W.S.), Wyoming state law, by citation. "6-2-101" is murder in the first degree (Title 6, Crimes and Offenses); "20-1-105" is divorce grounds (Title 20). Accepts natural forms: "6-2-101", "W.S. 6-2-101", "section 6-2-101". Returns the current statutory text, the section heading, and, where the source carries one cleanly, an enactment/amendment "history" note; many sections have no such note (Wyoming does not uniformly separate amendment history from body text). Wyoming publishes the CURRENT edition only; no historical/prior-year version is available online. Title 97 (the Constitution) is not covered, it uses "Article N, Section N" citations, a different scheme. Keyless. Use for "what does W.S. 6-2-101 say" or to check a Wyoming statute a case or contract 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": {
      "citation": "6-2-101"
    },
    "name": "wy_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, e.g. "6-2-101" (murder) or "20-1-105" (divorce grounds). Title-chapter-section, dash separated; a few titles carry a decimal (e.g. "34.1-1-101", Uniform Commercial Code).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description still adds real behavioral context: it returns current text plus heading, history notes only appear when the source carries them cleanly, and Wyoming publishes only the current edition. It does not discuss rate limits or error behavior for invalid citations, keeping it short of a 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-loaded with the core action and return contents, then caveats. It is dense but somewhat long, and the citation examples partially duplicate what the input schema already shows, costing a little efficiency.

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?

No output schema exists, so the description carries the return-value burden and does so: statutory text, section heading, and conditional history note. Combined with the coverage limits (current edition only, Title 97 excluded), an agent has everything needed to call it and interpret results.

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% and the schema already documents the dash-separated title-chapter-section format and the decimal-title case. The description adds value beyond the schema by noting accepted natural forms ("W.S. 6-2-101", "section 6-2-101"), which the schema does not state.

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 Wyoming Statutes") and scopes it to citation-based lookup, which cleanly separates it from a search-style sibling like wy_search. The examples of what a citation resolves to make the purpose concrete.

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 when-to-use cases ("what does W.S. 6-2-101 say", checking a statute a case or contract relies on) and explicit exclusions: Title 97/Constitution uses a different citation scheme, and no historical or prior-year editions exist. That is both positive and negative guidance.

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.