Skip to main content
Glama

Ar Statute

ar_statute
Read-onlyIdempotent

Get the TEXT of a section of the Arkansas Code (Ark. Code Ann.) by citation, state statutes, e.g. "5-10-101" (capital murder), "4-70-101". Accepts natural forms: "5-10-101", "Ark. Code Ann. 5-10-101", "ACA section 5-10-101". Returns the catchline, the operative statutory text, the "History." line (the Acts that enacted/amended it), and other legislative notes when present, case-law annotations are deliberately excluded (can run to hundreds of KB per heavily-litigated section). SOURCED FROM A 2020-11-06 RELEASE OF A PUBLIC-DOMAIN SOURCE, the official LexisNexis portal requires passing an authentication/CAPTCHA wall, so this is the newest free, non-walled text found; every response carries data_as_of and a staleness warning. Also returns later_acts: a dated, linked overlay of every act the Arkansas legislature's OWN Code-Sections-Amended index shows touching this exact citation since the 2020-11-06 snapshot (act number, session, PDF link), NOT merged into the text, explicitly labelled so, with sessions_checked naming every session the index covers even when later_acts is empty. Use for "what does ACA 5-10-101 say" or to check an Arkansas statute AND whether it has been amended since 2020-11-06. Keyless.

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": "5-10-101"
    },
    "name": "ar_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, title-chapter-section, e.g. "5-10-101" or "Ark. Code Ann. 4-70-101".

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 read-only/idempotent safety; the description adds substantial context beyond that: the 2020-11-06 public-domain snapshot, why LexisNexis is not used, the staleness warning and data_as_of field on every response, deliberate exclusion of case-law annotations to avoid huge payloads, and the later_acts overlay that is NOT merged into the text. This is exactly the kind of behavior an agent cannot infer from annotations.

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 purpose and citation form, and nearly every clause carries operational information. It is a dense single block, however, with some repetition around the later_acts labelling and the all-caps sourcing caveat; light structure or trimming would improve scanability.

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 takes on return-value disclosure itself and does it: catchline, operative text, History line, legislative notes, later_acts, sessions_checked, data_as_of. An agent knows both what it will get and the limits of that data.

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?

One parameter with 100% schema coverage sets a baseline of 3; the description earns above that by enumerating accepted citation formats ("5-10-101", "Ark. Code Ann. 5-10-101", "ACA section 5-10-101") that go beyond the schema's single example, plus the title-chapter-section shape.

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?

Names a specific verb and resource — retrieve the TEXT of a section of the Arkansas Code by citation — and grounds it in concrete citation forms and natural-language queries ("what does ACA 5-10-101 say"). The citation-lookup framing implicitly separates it from the ar_search sibling without needing an explicit contrast.

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 when-to-use guidance: quote a section, or check a statute AND whether it was amended since the 2020-11-06 snapshot. It does not name a when-not case or an explicit alternative tool, so it stops short of a 5.

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.