Skip to main content
Glama

Hi Search

hi_search
Read-onlyIdempotent

Search the Hawaii Revised Statutes BY TOPIC or keyword rather than citation, "landlord security deposit", "concealed firearm permit", "murder". Matches against the Legislature's own official section and chapter CATCHLINES across the whole Code (not full statutory prose, Hawaii does not publish a full-text search of statute body text, verified live), e.g. "landlord" surfaces sections like "Landlord's remedies for failure by tenant to pay rent" under chapter 521 (Residential Landlord-Tenant Code). Returns matching citations and catchlines; call hi_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": "hi_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?

Beyond the annotations (readOnly, idempotent, non-destructive, openWorld), the description discloses the critical matching limitation — it searches catchlines only, not statutory prose, and this was verified live — plus that it is keyless. It states the return shape (matching citations and catchlines). Not a 5 only because it says nothing about result ordering, empty-result behavior, or how broad-topic queries degrade.

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 verb and scope, then the key caveat, then the return value and next step. It is dense but each clause carries information; the parenthetical about Hawaii not publishing full-text search is slightly redundant with the earlier 'not full statutory prose' statement, which keeps it off a 5.

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 no output schema, the description correctly explains what comes back (citations and catchlines) and how to continue (hi_statute). For a 2-parameter keyless read tool, it covers purpose, limits, return shape, and next step — nothing essential 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, but the description adds real query semantics beyond the schema: the query is a topic or keyword, never a citation, with examples spanning distinct concepts ('concealed firearm permit', 'murder') and a note that matching is against catchline text, which tells the agent what phrasing to use. The limit parameter is left entirely to the schema.

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+resource+scope: search the Hawaii Revised Statutes by topic/keyword rather than citation, matching against official section and chapter catchlines across the whole Code. It explicitly excludes what it does not do (full statutory prose) and names the sibling hi_statute for full text, so an agent can distinguish it from alternatives without opening a 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?

Gives concrete when-to-use conditions ('BY TOPIC or keyword rather than citation') plus the routing rule: after getting a citation here, call hi_statute for the full text. It also discloses the boundary condition that full-text body search is unavailable, which prevents futile retries.

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.