Skip to main content
Glama

Nc General Statute

nc_general_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the North Carolina General Statutes, North Carolina state law, by citation. "N.C.G.S. 14-17" is first degree murder. Returns the statutory text with a data_as_of timestamp. Keyless. Use for "what does North Carolina General Statute 14-17 say" or to check an NC statute a case relies on.

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": {
      "section": "14-17"
    },
    "name": "nc_general_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "14-17" or "20-138.1". The chapter is the part before the first dash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 safety is covered. The description adds value beyond that: 'Keyless' discloses no auth is needed, and 'Returns the statutory text with a data_as_of timestamp' discloses the response shape, which has no output schema to cover it. No rate limits or error behavior mentioned.

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?

Three compact sentences, front-loaded with the core action, then a citation example, then the return/auth facts and usage triggers. No filler or repetition.

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?

For a one-parameter, keyless read tool with no output schema, the description covers action, input format, return content (text plus data_as_of), and usage triggers. Missing only edge behavior such as invalid citations or very long sections.

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 the single parameter's description already explains the citation format and chapter-before-dash rule. The description adds only the example 'N.C.G.S. 14-17' and a sample section, so it largely restates structured data — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 FULL TEXT of a section of the North Carolina General Statutes ... by citation') and anchors it with a concrete example ('N.C.G.S. 14-17'). The 'by citation' framing implicitly separates it from a statute-search sibling, but no sibling is named explicitly, so it stops short of a 5.

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 ('what does North Carolina General Statute 14-17 say' and 'to check an NC statute a case relies on'), which tells the agent when the tool is appropriate. It does not state when NOT to use it or name an alternative for keyword-style lookup, so no exclusion guidance.

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.