Skip to main content
Glama

Nc Constitution Search

nc_constitution_search
Read-onlyIdempotent

Find sections of the North Carolina Constitution by words in the heading or text, e.g. "eminent domain", "jury trial", "right to bear arms", "equal protection". Returns matching article and section numbers with headings and a short excerpt; call nc_constitution with the article and section for the verbatim text. Optionally restrict to one article. Keyless, live.

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": "jury trial"
    },
    "name": "nc_constitution_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25.
queryYesWords to find, e.g. "jury trial".
articleNoOptional: only search this article (1-14 or Roman numeral).

Output Schema

NameRequiredDescriptionDefault
hintNo
countNo
foundNo
queryNo
reasonNo
sourceNo
messageNo
partialNo
resultsNo
failuresNo
data_as_ofNo
searched_articlesNo
unreadable_articlesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/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 safety profile is covered. The description adds genuinely new context beyond that: the tool is "keyless, live," and it discloses the return shape (article and section numbers, headings, short excerpt) rather than full text, which prevents an agent from expecting verbatim content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, then the return shape and the follow-up call. The query examples are compact and directly useful; no sentence is filler.

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 keyless keyword-search tool with full schema coverage and an output schema, this covers everything an agent needs: what it searches, how to narrow it, what comes back, and which tool to call next for full text. Nothing material is missing.

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 description coverage is 100%, so the baseline is 3. The description echoes the article restriction ("Optionally restrict to one article") but adds no new semantics, and it never mentions the limit parameter or its default of 10 and max of 25, which the schema already handles.

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?

The description names a specific verb and resource ("Find sections of the North Carolina Constitution by words in the heading or text") and gives four concrete query examples, so it is immediately distinguishable from a general statute search. It also scopes the search (heading or text) precisely enough that an agent knows what matching means.

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?

It states the use case (keyword lookup inside the constitution), the optional narrowing ("restrict to one article"), and explicitly routes the agent onward: "call nc_constitution with the article and section for the verbatim text." That is an explicit alternative with the condition that selects it.

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.