Skip to main content
Glama

Nmi Statute

nmi_statute
Read-onlyIdempotent

Get the TEXT of a section of the Commonwealth Code of the Northern Mariana Islands (CNMI statutes) by citation, e.g. "6 CMC section 1101" (murder) or "6 CMC 1101". Accepts natural forms: "6 CMC 1101", "6 CMC section 1101", "Title 6 Section 1101". Returns the catchline and statutory text. Tries the official cnmilaw.org site live first; cnmilaw.org has been down since around 2026-10 (a registrar-level suspension, confirmed via both a normal connection and a Cloudflare edge probe) so most calls currently fall back to the Internet Archive Wayback Machine's own crawl of the same official PDF, every response says which route it used, with data_as_of and a staleness warning on the fallback. Use for "what does 6 CMC 1101 say" or to check a Northern Mariana Islands statute.

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": "6 CMC 1101"
    },
    "name": "nmi_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, e.g. "6 CMC 1101" or "6 CMC section 1101" (title 1-10, then section number).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / citation / description
      Previous value: -"Section citation, e.g. \"6 CMC 1101\" or \"6 CMC § 1101\" (title 1-10, then section number)."New value: +"Section citation, e.g. \"6 CMC 1101\" or \"6 CMC section 1101\" (title 1-10, then section number)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: a live-first cnmilaw.org attempt, a documented Wayback Machine fallback with the reason for the outage, and per-response route disclosure plus data_as_of and a staleness warning. That is exactly the reliability and provenance context an agent needs and annotations cannot convey.

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 primary action, format, and return values before operational detail. The outage explanation is a long run-on parenthetical, but every sentence carries information an agent would otherwise have to discover at call time.

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 single-parameter lookup with no output schema, the description covers input formats, return contents (catchline and statutory text), provenance fields, and degraded-mode behavior. Nothing needed 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, but the description adds accepted citation variants not fully enumerated in the schema ("Title 6 Section 1101") and confirms title range 1-10. It stops short of describing failure behavior for malformed or out-of-range citations.

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 the TEXT of a section of the Commonwealth Code of the Northern Mariana Islands") plus scope (by citation, returns catchline and statutory text). The phrase "by citation" and the concrete examples distinguish it from the search-oriented sibling without needing to name it.

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 clear use cases: "Use for 'what does 6 CMC 1101 say' or to check a Northern Mariana Islands statute." It does not name alternatives or state when not to use it (e.g. when the citation is unknown and nmi_search would be better), so it falls short of a 5.

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.