Skip to main content
Glama

Ar Sentencing Grid

ar_sentencing_grid
Read-onlyIdempotent

Arkansas felony SENTENCING STANDARDS GRID: the presumptive sentence range for a seriousness level (1-10) and criminal history score (0-5+), from the Arkansas Sentencing Commission. Answers "presumptive sentence range at seriousness level 10, criminal history category III", "Arkansas sentencing grid level 7 score 2", "how many months for a level 6 felony with 4 prior points". With criminal_history_score returns that cell: the presumptive prison (ADC) range in months and years when the grid presumes one, the sanction types the cell allows (ADC = Department of Correction facility, CCC = Community Correction Center, AS = alternative sanctions), the grid edition and effective date (offenses committed on or after 2018-01-01), release/transfer eligibility notes, the statutory range by felony class, and offenses the Commission lists at that level. Without a score returns all six cells of the level. This is the Commission's presumptive grid, not the habitual-offender statute (5-4-501) and not a prediction of the sentence a court will impose. Use ar_offense_seriousness to find an offense's level. 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": {
      "seriousness_level": 10,
      "criminal_history_score": "3"
    },
    "name": "ar_sentencing_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriousness_levelYesOffense seriousness level, 1 (lowest) to 10 (highest).
criminal_history_scoreNoCriminal history score 0, 1, 2, 3, 4 or "5+" (category III = score 3). Omit for all six.

Output Schema

NameRequiredDescriptionDefault
stateNo
legendNo
sourceNo
editionNo
summaryNo
data_as_ofNo
offenses_noteNo
index_captured_atNo
sanctions_allowedNo
seriousness_levelNo
grid_effective_dateNo
grid_effective_textNo
presumes_prison_termNo
statutory_range_yearsNo
criminal_history_scoreNo
presumptive_range_yearsNo
presumptive_range_monthsNo
release_and_transfer_notesNo
offenses_listed_at_this_levelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered; the description adds real context beyond them — the grid edition and effective date (2018-01-01), release/transfer eligibility notes, the ADC/CCC/AS sanction terminology, and the behavioral difference between passing a score (one cell) and omitting it (all six cells). What it doesn't do is describe pagination or response size, though the output schema covers return shape.

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 the return payload, then caveats, then the sibling pointer — good ordering with no filler prose. It is, however, verbose in places, and three near-identical example queries (level 10/III, level 7 score 2, level 6 with 4 points) convey the same information as one would.

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?

For a two-parameter lookup with annotations and an output schema already supplied, the description covers everything an agent needs: what the cell contains, what a scoreless call returns, the effective date, the legal scope limit, and the prerequisite lookup. No material gap remains.

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 description coverage is 100% and already documents both parameters, including the 1-10 range and the "5+" option, so the baseline is 3. The description reinforces the semantics (category III = score 3) and restates the omit-behavior for criminal_history_score, but adds no syntax or edge-case detail the schema lacks.

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 resource (Arkansas felony Sentencing Standards Grid) and the exact lookup it performs — presumptive sentence range by seriousness level (1-10) and criminal history score (0-5+). The named dimensions and the source (Arkansas Sentencing Commission) make it immediately distinguishable from siblings like ar_statute or ar_offense_seriousness.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent elsewhere for the upstream step ("Use ar_offense_seriousness to find an offense's level") and states two clear exclusions: it is not the habitual-offender statute 5-4-501 and not a prediction of an imposed sentence. Those are exactly the when-not conditions an agent needs before relying on the output.

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.