Skip to main content
Glama

Az Revised Statute

az_revised_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Arizona Revised Statutes, Arizona state law, by citation. "A.R.S. 13-1105" is first degree murder. Returns the statutory text. Keyless. Use for "what does Arizona Revised Statute 13-1105 say" or to check an Arizona 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": "13-1105"
    },
    "name": "az_revised_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "13-1105" or "28-1381". Title is the part before the dash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds operational context beyond that: "Keyless" (no authentication setup needed) and the fact that the response is the statutory text itself rather than a summary or citation list. It omits what happens for a bad or nonexistent citation, which keeps it from 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?

Short and front-loaded, leading with the action and the FULL TEXT scope before examples. Minor redundancy: "Returns the statutory text" restates "Get the FULL TEXT," and "Arizona Revised Statutes, Arizona state law" doubles up the jurisdiction naming.

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 one-parameter read tool with no output schema, the description conveys scope (full statutory text), input form, and a worked example, which is enough to call it correctly. The only real gap is error behavior for unresolvable citations, which is minor here.

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% and the schema already explains the section format including that the title is the part before the dash. The description reinforces this with a cited example, but adds no syntax, alias, or formatting rules beyond what the schema provides, so the baseline of 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?

States a specific verb and resource: retrieve the FULL TEXT of an Arizona Revised Statutes section by citation, and grounds it with a concrete example ("A.R.S. 13-1105" is first degree murder). No sibling tool in the list covers statutes, so an agent can route to it unambiguously.

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 an explicit use case in the user's own phrasing ("what does Arizona Revised Statute 13-1105 say") plus a secondary use: verifying an Arizona statute a case relies on. It does not name exclusions or alternatives, but the tool's domain is narrow enough that no plausible alternative exists among the siblings.

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.