Skip to main content
Glama

Ar Search

ar_search
Read-onlyIdempotent

Search the Arkansas Code BY TOPIC or keyword over official section catchlines (section titles), not citation, e.g. "capital murder", "security deposit", "concealed carry". Returns matching citations and catchlines; call ar_statute with a citation for the full text. Catchline search only (not full statutory- text search), a query that never appears in any catchline will return no matches even if the underlying topic is discussed inside a section's body. Sourced from the same 2020-11-06 release as ar_statute. 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": "murder"
    },
    "name": "ar_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 50.
queryYesTopic or keywords, e.g. "security deposit".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description still adds real behavior beyond them: the index is catchline-only, so queries matching only body text return no results, it shares the 2020-11-06 release with ar_statute, and it needs no API key. The only mild gap is that result count/pagination behavior is not described.

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?

The critical scope constraint is front-loaded and the follow-up call to ar_statute follows immediately, which is the right order. There is some redundancy: 'BY TOPIC or keyword over official section catchlines, not citation' is restated later as 'Catchline search only (not full statutory-text search)', costing a few words.

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 search tool this covers everything an agent needs: what is indexed, what is returned (citations and catchlines), what to call next, the false-negative failure mode, data freshness, and keyless access. No output schema exists, but the return contents are stated explicitly in prose.

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 further by explaining that `query` is matched against catchlines specifically and by supplying several realistic example phrases. The `limit` parameter is left entirely to the schema, which already documents default 10 and max 50.

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 (Search) and resource (Arkansas Code) and narrows scope precisely: over official section catchlines (section titles), not citation. It also names the sibling it hands off to (ar_statute) for full text, so an agent can distinguish it from other search tools.

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: use this tool for topic/keyword lookup, then call ar_statute with a returned citation for full statutory text. It also gives the negative condition — citation lookups are not this tool — and names concrete example queries, leaving nothing to infer.

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.