Skip to main content
Glama

Nmi Search

nmi_search
Read-onlyIdempotent

Search the Commonwealth Code of the Northern Mariana Islands BY TOPIC or keyword over official section catchlines (section titles), not citation, e.g. "murder", "security deposit", "driver license". Returns matching citations and catchlines; call nmi_statute with a citation for the full text. Catchline search only (not full statutory-text search)a query that never appears in any catchline returns no matches even if the topic is discussed inside a section's body.

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": "murder"
    },
    "name": "nmi_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 50.
queryYesTopic or keywords, e.g. "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, open-world, non-destructive behavior, so the bar is lower. The description still adds the critical non-obvious trait that this searches catchlines only and silently returns zero matches for body-text-only topics, plus what the result contains (citations and catchlines). It does not mention result ordering or how limit interacts with truncation.

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 purpose, then the return shape, then the limitation, so an agent can stop reading early. Slightly penalized for redundancy ("not citation" and "Catchline search only" restate the same constraint) and a run-together sentence fragment where the parenthetical abuts the next clause.

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-only search with no output schema, the description covers purpose, query semantics, the return shape, the key failure mode, and the follow-up tool. 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, but the description adds real meaning: the query is a topic/keyword string, explicitly not a citation, with illustrative examples. The limit parameter is left entirely to the schema, which already documents default and max.

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 (search) and resource (Commonwealth Code of the Northern Mariana Islands section catchlines), and explicitly scopes it to topics/keywords rather than citations. That scope statement plus the handoff to nmi_statute makes it distinguishable from siblings without opening any 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/keyword queries over catchlines) and when to use the alternative (call nmi_statute with a citation for full text). It also gives a clear negative case: queries that never appear in a catchline return nothing even if the topic is discussed in a section body.

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.