Skip to main content
Glama

Nc Constitution

nc_constitution
Read-onlyIdempotent

Get the VERBATIM text of the North Carolina Constitution (state constitution, not statutes) by article and section, e.g. Article I Section 19 (law of the land; equal protection) or Article I Section 25 (right of jury trial in civil cases). Give the article (1-14 or Roman numeral) and a section number to get that section exactly as the North Carolina General Assembly publishes it; give only the article to list its sections and headings (use this when unsure which section number a topic is under, such as eminent domain). Returns heading, text and link. The publisher page carries the current Constitution text without amendment history. 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": {
      "article": "1",
      "section": "19"
    },
    "name": "nc_constitution"
  }
}

Input Schema

NameRequiredDescriptionDefault
articleYesArticle number 1-14 or Roman numeral, e.g. "1", "I", "Article I".
sectionNoSection number within the article, e.g. "19". Omit to list the article's sections.

Output Schema

NameRequiredDescriptionDefault
urlNo
hintNo
noteNo
textNo
foundNo
introNo
reasonNo
sourceNo
articleNo
headingNo
messageNo
sectionNo
citationNo
documentNo
sectionsNo
variantsNo
data_as_ofNo
text_charsNo
attributionNo
jurisdictionNo
article_titleNo
section_countNo
variants_noteNo
article_numberNo
available_sectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds real context beyond the read-only/idempotent annotations: it discloses that text is reproduced VERBATIM as the General Assembly publishes it, that the page carries current text without amendment history, and that access is keyless and live. It does not discuss rate limits or failure modes.

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 purpose, then modes, then return fields and data caveats; nearly every sentence earns its place. The parenthetical examples make it slightly dense but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the two modes, the return shape (heading, text, link), and the important caveat that amendment history is absent. With an output schema present, return-value detail is not required; remaining gap is only deeper behavioral/error disclosure.

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 already documents both parameters including the omit-section behavior and accepted article formats, so the description's parameter content largely restates it. The added value is minimal despite the concrete example call.

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 VERBATIM text of the North Carolina Constitution... by article and section', and explicitly distinguishes it from statutes ('state constitution, not statutes'), which separates it from nc_general_statute and the search siblings.

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?

Gives explicit operating modes: article+section for exact text, article alone to list sections and headings, plus a concrete trigger for the listing mode ('use this when unsure which section number a topic is under, such as eminent domain').

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.