Skip to main content
Glama

Ak Statute

ak_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Alaska Statutes (Alaska Code) by citation. "4.11.010" (AS 04.11.010) is alcohol-license requirements; "11.41.100" (AS 11.41.100) is murder in the first degree. Accepts natural forms: "4.11.010", "AS 04.11.010", "Alaska Statutes 11.41.100". Returns the current statutory text, the official catchline, and title/chapter context. Alaska publishes the CURRENT text only through this endpoint, no amendment-history line and no historical (pre-amendment) version; this tool says so rather than guessing. Keyless. Use for "what does AS 11.41.100 say" or to check an Alaska statute a case or lease 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": "4.11.010"
    },
    "name": "ak_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, title.chapter.section, e.g. "4.11.010" (alcohol licensing) or "11.41.100" (murder).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safe-read profile; the description adds substantive behavior: keyless access, the exact return payload (statutory text, official catchline, title/chapter context), and the critical limitation that no amendment-history line or pre-amendment version is available. It explicitly commits to reporting that gap rather than fabricating, which is exactly the kind of disclosure an agent needs.

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 examples, then boundaries. It is a dense single paragraph with little waste, though the aside "this tool says so rather than guessing" is slightly chatty and the title/chapter context detail edges toward redundancy with the return-value sentence.

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?

There is no output schema, so the description carries the burden of describing return values — which it does fully (text, catchline, title/chapter context). Combined with the currency limitation and keyless note, 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 goes beyond the schema by listing accepted input forms ("4.11.010", "AS 04.11.010", "Alaska Statutes 11.41.100"), which the schema does not mention. That materially reduces format-guessing on the single required parameter.

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 a section of the Alaska Statutes by citation — and grounds it with two concrete examples (4.11.010 alcohol licensing, 11.41.100 murder). An agent can tell this apart from a general search tool like ak_search without opening the schema.

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?

Explicitly names use cases: "what does AS 11.41.100 say" or verifying an Alaska statute a case or lease relies on. It also states the coverage boundary (current text only, no amendment history). It does not, however, say when to prefer ak_search over a direct citation lookup, so the routing against the sibling is left implicit.

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.