Skip to main content
Glama

Al Search

al_search
Read-onlyIdempotent

Search the Code of Alabama 1975 BY TOPIC or keyword rather than citation, "landlord security deposit", "concealed pistol permit", "homicide". This is a REAL FULL-TEXT search over actual section body text (not just captions) run live against the Alabama Legislature's own search index, confirmed to surface sections whose title never mentions the search term. Returns matching citations, titles and a text snippet; call al_statute with a citation for the full 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": {
      "query": "landlord"
    },
    "name": "al_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 25.
queryYesTopic or keywords, e.g. "landlord 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 description is not carrying the safety burden. It still adds real value beyond them: the search runs live against the Alabama Legislature's index, matches section body text rather than captions only, and is keyless (no auth needed). It stops short of describing result ordering or how snippets are chosen, which keeps it off a 5.

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?

Purpose and scope are front-loaded in the first clause, and the pointer to al_statute arrives before the trailing note. It is slightly padded — the emphasized "REAL FULL-TEXT" phrasing and repeated example queries cost a few words without adding information — but nothing is genuinely wasteful.

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 with no output schema, the description covers what it searches, how it searches, what it returns (citations, titles, snippet), and where to go next for full text. Nothing an agent needs in order to call it correctly is missing.

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. The description adds meaning beyond the schema by framing the query parameter as topic/keywords rather than a citation string and by illustrating the intended query style, which affects how an agent should phrase input.

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 Code of Alabama 1975") and immediately scopes it to topic/keyword rather than citation, with concrete example queries. It also names the sibling al_statute as the follow-up for full text, so an agent can distinguish the two 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?

Explicitly says when to use this tool (topic or keyword lookups, not citation lookups) and gives the alternative path: "call al_statute with a citation for the full text." The when/when-not split is unambiguous.

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.