Skip to main content
Glama

Hi Statute

hi_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Hawaii Revised Statutes (HRS), Hawaii state law, by citation. "707-701" is murder in the first degree; "521-44" is a landlord's security-deposit duty under the Residential Landlord-Tenant Code. Accepts natural forms: "707-701", "HRS 707-701", "section 707-701". Returns the current statutory text, the official catchline, chapter context, and amendment/enactment history parsed from the Legislature's own "[L 1972, c 9, ...]" session-law bracket. Pass "year" (1999-2025) to get that year's historical archived text of the same section instead of the current one, Hawaii publishes a full year-by-year online archive. Keyless. Use for "what does HRS 707-701 say" or to check a Hawaii statute a case or lease relies on, now or as of a past year.

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": {
      "citation": "707-701"
    },
    "name": "hi_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional: a historical year (1999-2025) to fetch that year's archived text instead of the current one.
citationYesSection citation, chapter-section, e.g. "707-701" (murder) or "521-44" (security deposits). Some sections carry a decimal suffix, e.g. "521-69.5".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/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 bar is low, yet the description adds real value: keyless access, an unusually rich return payload (text, catchline, chapter context, session-law amendment history) and the fact that 'year' switches to Hawaii's archived historical text.

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 action ('Get the FULL TEXT'), then examples, then return contents, then the year option. Dense but every clause carries information; the doubled quotation marks in the session-law bracket example are the only noise.

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?

No output schema exists, so the description must explain return values and it does - text, catchline, chapter context, amendment history - plus the historical-mode behavior, leaving nothing an agent needs to call it correctly.

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 exceeds it by enumerating accepted citation forms ('707-701', 'HRS 707-701', 'section 707-701') that the schema does not spell out, and by clarifying that 'year' substitutes archived text rather than supplementing it.

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 (get full text of an HRS section by citation) and backs it with two concrete citation examples (707-701 murder, 521-44 security deposits), which clearly separates it from a general search tool like hi_search.

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?

Gives explicit use cases ('what does HRS 707-701 say', verifying a statute a case or lease relies on, current vs. past year). It never says what to do when only a topic is known rather than a citation - e.g., pointing to hi_search - so routing guidance is slightly incomplete.

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.