Skip to main content
Glama

Ok Statute

ok_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Oklahoma Statutes by citation, e.g. "21-701.7" (Murder in the First Degree) or "41-111" (termination of tenancy). Accepts "21-701.7", "21 O.S. 701.7", or "21 O.S. section 701.7". Returns the current statutory text, its chapter breadcrumb, the "Cite as" line, its full amendment history (every amending Act), and a historical_versions list of every prior (superseded) version with a citeid you can pass back as version_citeid to retrieve that EXACT prior text. Keyless. Use for "what does 21 O.S. 701.7 say", "Oklahoma murder statute", or to check an Oklahoma statute a case or contract relies on, including how it read before a given amendment.

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": "21-701.7"
    },
    "name": "ok_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation as title-section, e.g. "21-701.7" or "41-111". The title is the part before the dash/space and may carry a letter suffix (e.g. "10A-1" or "85A-45").
version_citeidNoOptional. A "citeid" value from a previous result's historical_versions array, fetches that superseded version's exact text instead of the current one. When set, "citation" is optional (used only to label the response).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / version_citeid / description
      Previous value: -"Optional. A \"citeid\" value from a previous result's historical_versions array — fetches that superseded version's exact text instead of the current one. When set, \"citation\" is optional (used only to label the response)."New value: +"Optional. A \"citeid\" value from a previous result's historical_versions array, fetches that superseded version's exact text instead of the current one. When set, \"citation\" is optional (used only to label the response)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare read-only/idempotent/open-world) by describing the exact payload: current statutory text, chapter breadcrumb, 'Cite as' line, full amendment history, and a historical_versions list with citeids usable as version_citeid to retrieve superseded text verbatim. It also discloses the keyless/no-auth property, which annotations do not cover.

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 example citations, then the return contract. It is a single dense paragraph with a slightly long tail of quoted usage phrasings, but every sentence 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 no output schema present, the description carries the full burden of describing returns and does so thoroughly — text, breadcrumb, cite-as line, amendment history, and historical versions. Combined with 100% parameter coverage, an agent has everything needed to call it and interpret the result.

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 the operational relationship the schema only states mechanically: historical_versions citeids round-trip into version_citeid to fetch that EXACT prior text. It also demonstrates accepted citation spellings, which helps an agent format the citation parameter correctly.

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 Oklahoma Statutes by citation') and immediately grounds it with concrete citation examples including subject matter ('21-701.7' Murder in the First Degree). It is clearly distinguishable from a keyword-search sibling like ok_search because it retrieves one cited section rather than searching.

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 explicit when-to-use triggers: 'what does 21 O.S. 701.7 say', 'Oklahoma murder statute', and checking a statute a case or contract relies on, including pre-amendment readings. It stops short of naming an alternative tool (e.g. ok_search) for the keyword-lookup case, so the routing guidance is clear but not fully exclusive.

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.