New Jersey Code

Nj Statute Section

nj_statute_section

Read-onlyIdempotent

Get the FULL TEXT of a section of the New Jersey Statutes (N.J.S.A.) — New Jersey state law — by citation, plus its amendment history where the source lists one. "N.J.S.A. 2C:11-3" is murder; "39:4-50" is driving while intoxicated; "46:8-1" is a landlord-tenant statute. Returns the statutory text, a parsed amendment_history line when the section has been amended (empty for an original, unamended section), and says explicitly that a prior point-in-time version is not available through this source. Keyless. Use for "what does N.J.S.A. 39:4-50 say" or to check a citation a case or bill 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": "39:4-50"
    },
    "name": "nj_statute_section"
  }
}

Input Schema

Name	Required	Description	Default
`section`	Yes	Section as cited, e.g. "2C:11-3" (murder), "39:4-50" (DWI), or "46:8-19" (security deposits). The part before the colon is the Title.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description goes well beyond them: it discloses the return composition (statutory text, parsed amendment_history line, empty for unamended sections), flags the limitation that no prior point-in-time version is available from this source, and notes the tool is keyless. That is exactly the additional context the annotations cannot carry.

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 action and resource, then returns, then usage. It is dense and every sentence carries information, though the citation examples are duplicated verbatim in the schema, costing a little redundancy.

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?

With no output schema, the description carries the full burden of describing return values and does so explicitly — statutory text, amendment history (including the empty case), and the absence of point-in-time versions. An agent has everything needed to call it and interpret the result.

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% for the single 'section' parameter, so the baseline is 3. The description's citation examples and the 'part before the colon is the Title' note largely restate what the schema already documents, adding no new syntax or format rules.

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 FULL TEXT of a section of the New Jersey Statutes (N.J.S.A.) by citation, plus its amendment history.' Concrete citation examples ('2C:11-3' is murder) make the scope unambiguous and let an agent distinguish this direct-lookup tool from the sibling nj_statute_search.

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 explicit triggers: 'Use for "what does N.J.S.A. 39:4-50 say" or to check a citation a case or bill relies on.' The 'by citation' framing implies the caller must already have a citation, which quietly routes citation-less queries elsewhere, but the sibling search tool is never named and no when-not-to-use condition is stated.

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

All New Jersey Code tools Inspect

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.