Skip to main content
Glama

Ak Search

ak_search
Read-onlyIdempotent

Search the Alaska Statutes BY TOPIC or keyword rather than citation, "alcohol license", "murder", "child custody". Matches against the Alaska Legislature's own official CHAPTER catchlines (942 of them, across all 47 titles), NOT full statutory text or per-section catchlines; akleg.gov exposes neither keylessly (verified live). Returns matching title/chapter and the chapter catchline; call ak_statute with a full citation (you supply the section number) for the actual text. 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": {
      "limit": 10,
      "query": "insurance"
    },
    "name": "ak_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 25.
queryYesTopic or keywords, e.g. "alcohol license".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description instead adds substantive behavior the annotations cannot express: matching is against chapter catchlines only (942 across 47 titles), not full text or per-section catchlines, and the source exposes neither keylessly. The one gap is that it does not describe result ordering, ranking, or how partial matches are handled, which matters for an openWorld search.

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-loads the core distinction (topic vs. citation) and follows with scope and the fallback tool, which is the right order. It is dense with parentheticals — '(verified live)' and the 942/47-titles figure — that add credibility but slightly clutter an otherwise efficient definition.

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 only two parameters and no output schema, the description closes the loop by stating what is returned (matching title/chapter plus the chapter catchline) and how to get the full text afterwards. Nothing an agent needs in order to call this correctly, or to interpret the result, is left unstated.

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%, so both parameters are already documented — including the limit default of 10 and max of 25. The description's phrase 'topic or keyword' and its example reinforce the query intent but add no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 ('Search the Alaska Statutes BY TOPIC or keyword') and immediately contrasts it with citation-based lookup, naming ak_statute as the alternative. An agent can distinguish it from the sibling without opening either schema.

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?

Explicit routing: use this tool for topic/keyword discovery, then call ak_statute with a full citation to get actual statutory text. It also rules out an inference an agent might otherwise make — that this searches full statutory text — and supplies the positive use case with concrete query examples.

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.