Skip to main content
Glama

Gu Statute

gu_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Guam Code Annotated (GCA), Guam territorial law, by citation. "9 GCA 16.30" (or "9 GCA section 16.30") is Aggravated Murder Defined; "21 GCA 33101" is who may take an acknowledgment of a deed. Guam uses TWO citation styles depending on the title: newer titles write "chapter.section" with a dot (9 GCA, the Criminal Code); older titles concatenate chapter and a zero-padded section number with no separator (e.g. 21 GCA). Either form works. If the citation omits "N GCA", pass title separately (1-22). Returns the current statutory text, the official catchline, chapter/title context, source PDF URL, and data_as_of. Guam publishes the CURRENT text only, no per-year historical archive; this tool says so rather than guessing. Keyless. Use for "what does 9 GCA 16.30 say" or to check a Guam statute a case or contract relies on.

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": "9 GCA 16.30"
    },
    "name": "gu_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoGCA Title number (1-22), only needed if not already included in `citation` (e.g. citation="16.30", title=9).
citationYesSection citation, e.g. "9 GCA 16.30", "9 GCA section 16.30", "21 GCA 33101", or a bare "16.30" / "33101" with `title` given separately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / citation / description
      Previous value: -"Section citation, e.g. \"9 GCA 16.30\", \"9 GCA § 16.30\", \"21 GCA 33101\", or a bare \"16.30\" / \"33101\" with `title` given separately."New value: +"Section citation, e.g. \"9 GCA 16.30\", \"9 GCA section 16.30\", \"21 GCA 33101\", or a bare \"16.30\" / \"33101\" with `title` given separately."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so safety is covered. The description adds genuinely new context: keyless access, Guam's current-text-only publication policy and that the tool reports this rather than guessing, plus what the response includes (statutory text, catchline, chapter/title context, source PDF URL, data_as_of).

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 verb, resource, and a worked example, then layers citation-format rules and caveats. Dense but nearly every clause carries information; the two illustrative statute examples cost a little length but earn it by disambiguating the format.

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 read tool with no output schema, this covers input formats, the optional-title fallback, the currency limitation, and the shape of returned data. An agent can call it correctly on the first attempt without consulting anything else.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description still adds substantive meaning: it explains Guam's two competing citation styles (dot-separated 'chapter.section' in newer titles like 9 GCA vs zero-padded concatenation in older titles like 21 GCA) and states both forms work. It also clarifies exactly when `title` is required (citation omits 'N GCA', valid 1-22).

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?

Opens with a specific verb and resource ('Get the FULL TEXT of a section of the Guam Code Annotated') and immediately grounds it in a concrete citation example, so an agent knows exactly what it retrieves. The distinction from a fuzzy search tool is implicit but the retrieval-by-citation framing is unambiguous.

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 when-to-use phrasing ('Use for "what does 9 GCA 16.30 say" or to check a Guam statute a case or contract relies on') and a clear scope limitation (current text only, no historical archive). It does not name a sibling alternative for keyword searching, so routing guidance is one-sided.

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.