Skip to main content
Glama
Sign In

NC General Statutes

by com.ncstatutes
OverviewDiscussionsAdmin

What a North Carolina (NC) statute cites, and what cites it

cross_references
Read-onlyIdempotent

Which North Carolina (NC) statutes this section cites, and which cite it.

Use for "what does G.S. 14-72.1 depend on" or "what else references it". OUTBOUND is what the section's own text cites; INBOUND is every section citing it — the direction you cannot get by reading one statute.

Section-level only: a reference to 20-141(j1) is an edge to 20-141. Chapter-wide and "this Article" references are not edges. For the text itself use get_statute.

Input Schema

NameRequiredDescriptionDefault
limitNo
citationYesThe section whose references you want, in either direction.
directionNoboth

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / citation / examples
      Previous value: -[
-  "15A-145.5",
-  "G.S. 1A-1"
-]New value: +[
+  "15A-145.5",
+  "G.S. 1A-1",
+  "8C-1, Rule 702"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds real value beyond them by disclosing edge semantics: section-level only, with chapter-wide and 'this Article' references excluded, and clarifying OUTBOUND vs INBOUND directionality.

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 purpose, then usage examples, then the scope caveat and sibling pointer. Sentences are tight and each carries information, with only mild repetition between the opening line and the examples.

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?

An output schema exists, so return values need not be described. The description covers purpose, usage, directionality, and inclusion/exclusion scope; the only meaningful omission is the semantics of the 'limit' parameter.

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 only 33%, so the description must compensate. It explains the 'direction' concept (OUTBOUND/INBOUND, default both), but the 'limit' parameter is undocumented in both the schema and the description, leaving a clear gap.

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: which NC statutes a section cites and which cite it. It also differentiates from siblings by directing text lookups to get_statute, so an agent can route without opening the schema.

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?

Provides concrete example queries ('what does G.S. 14-72.1 depend on', 'what else references it') and names get_statute as the alternative for raw text. Clear context is given, though there is no explicit when-not beyond the text-lookup case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NC General Statutes toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Directories

Resources