Skip to main content
Glama

Nc Statute Search

nc_statute_search
Read-onlyIdempotent

Search North Carolina General Statutes BY TOPIC or keyword rather than citation, "election conduct at polling places", "landlord retaliatory eviction", "concealed handgun permit". Returns ranked sections with their citations; use nc_general_statute afterward for the full text of one. Full-text search, so it answers questions no citation lookup can. 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": "concealed handgun permit"
    },
    "name": "nc_statute_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25.
queryYesTopic or keywords, e.g. "election conduct at polling places".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds return shape (ranked sections with citations), the fact that matching is full-text, and that access is keyless (no credentials) — useful context beyond structured fields, though rate limits and ranking behavior are unstated.

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-plus-resource and the topic-vs-citation distinction, and the handoff to nc_general_statute comes early. The repeated quoted example phrases are slightly redundant with the query parameter's own example, costing a little tightness.

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 search tool with full schema coverage, the definition covers purpose, selection guidance, return format and keyless access. Since no output schema exists, describing the ranked-sections return is exactly the missing piece that is supplied.

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

Parameters3/5

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

Schema coverage is 100% and both parameters (query, limit) are documented in the schema, so the baseline is 3. The description reinforces the semantics of query as topic/keyword phrasing via worked examples but says nothing about limit that the schema doesn't already cover.

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 (North Carolina General Statutes) plus the key differentiator: search BY TOPIC or keyword rather than citation. Example queries and the contrast with citation lookup make it distinguishable from nc_general_statute without opening either 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 routes the agent: use this tool for topic/keyword questions, then use nc_general_statute afterward to fetch full text of one section. It also names the case this answers that citation lookup cannot, so when-to-use versus alternatives is unambiguous.

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.