Skip to main content
Glama

Ar Offense Seriousness

ar_offense_seriousness
Read-onlyIdempotent

Find the Arkansas SENTENCING SERIOUSNESS LEVEL (1-10) of a felony offense by statute citation or offense name, from the Arkansas Sentencing Commission's offense seriousness ranking table. Answers "what seriousness level is aggravated robbery in Arkansas", "level of 5-12-103", "Arkansas sentencing ranking for Murder 1st degree". Each match returns the statute, felony class, offense name, ranking level, percent of sentence to serve, statutory designations (A 70% offense, B possible 70% offense, C serious violent felony, D violent felony, E 100% felon in possession), and start/end dates when the ranking or offense changed. Pass the level to ar_sentencing_grid for the presumptive range. Matches by statute prefix ("5-10-102") or by every word of the name. 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": {
      "query": "aggravated robbery"
    },
    "name": "ar_offense_seriousness"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 25, max 100.
queryYesStatute citation ("5-12-103") or offense name words ("aggravated robbery").

Output Schema

NameRequiredDescriptionDefault
nextNo
countNo
foundNo
queryNo
sourceNo
resultsNo
data_as_ofNo
total_matchesNo
index_captured_atNo

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 cover read-only, idempotent, and open-world, but the description adds genuinely new behavior: matching is by statute prefix or by every word of the name, 'Keyless' means no API key is required, and results include designations and date ranges when a ranking changed. It stops short of describing no-match behavior or result ordering.

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 answer and followed by example questions and the sibling handoff. The long parenthetical enumeration of returned fields is dense but useful; a few phrases could be trimmed without loss.

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 read-only lookup with an output schema and full annotation coverage, the description supplies everything an agent needs: source authority, accepted query forms, matching semantics, result fields, and the natural next tool.

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, and the description earns one more by explaining the matching rules that the schema does not: a statute citation matches by prefix, while an offense name must match every word. The limit parameter is left entirely to the schema, which is acceptable given its own description.

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 ('find the Arkansas sentencing seriousness level of a felony offense'), names the source table, and gives concrete example queries. It is clearly distinct from siblings like ar_statute (full statute text) and ar_sentencing_grid (range lookup) because the level-to-grid handoff is explicit.

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?

Tells the agent exactly what to do next ('Pass the level to ar_sentencing_grid for the presumptive range') and shows the query shapes that trigger it. It never states a when-not condition or a fallback if the offense is not found, which keeps it 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.