Skip to main content
Glama

Al Statute

al_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Code of Alabama 1975, Alabama state law, by citation. "13A-6-2" is murder; "35-9A-204" covers a landlord's duty to maintain the premises. Accepts natural forms: "13A-6-2", "Ala. Code 13A-6-2", "section 13A-6-2". Returns the current statutory text, section title, the Legislature's own amendment-history citation list (amendment_history), and, when an Act has already been enacted but is not yet in force, a forward-looking pending_version with its future effective date. Alabama publishes CURRENT text only going backward, so a pre-amendment (historical) version of the text is not available; this tool says so rather than guessing. Keyless. Use for "what does Ala. Code 13A-6-2 say" or to check an Alabama 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": "13A-6-2"
    },
    "name": "al_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, title-chapter-section, e.g. "13A-6-2" (murder) or "35-9A-204" (landlord duty to maintain premises). Titles can carry a letter, e.g. "13A".

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?

Adds substantial context beyond the annotations: keyless access, the returned fields (statutory text, section title, `amendment_history`), and the existence of a forward-looking `pending_version` with a future effective date. It also discloses a real limitation — Alabama publishes current text only, so historical versions are unavailable — and says the tool reports that rather than guessing, which is exactly the kind of behavior an agent cannot infer from readOnly/openWorld hints.

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, then examples, return shape, and limitations in a logical order. It is dense but nearly every sentence carries information; the murder example is repeated from the schema, a minor redundancy.

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, the description carries the return-value burden and does so by naming the four things returned plus the pending/historical-text caveats. For a single-parameter lookup tool, 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 baseline is 3, but the description adds genuine value: it lists accepted natural forms ("13A-6-2", "Ala. Code 13A-6-2", "section 13A-6-2"), telling the agent input normalization is tolerated. It does not address malformed or non-existent citations explicitly.

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 precise verb and resource: "Get the FULL TEXT of a section of the Code of Alabama 1975 ... by citation." The two citation examples ("13A-6-2" murder, "35-9A-204" landlord duty) make the exact-lookup nature concrete, which implicitly separates it from a search-style sibling without the agent needing to open a 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?

Gives clear triggering contexts: "Use for 'what does Ala. Code 13A-6-2 say' or to check an Alabama statute a case or lease relies on." It also states a boundary condition — pre-amendment historical text is unavailable. It stops short of explicitly naming an alternative tool for full-text searching by keyword.

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.