Skip to main content
Glama
Sign In

New Jersey Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Nj Statute Search

nj_statute_search
Read-onlyIdempotent

Search the New Jersey Statutes (N.J.S.A.) BY TOPIC or keyword rather than citation — "security deposit interest", "landlord grounds for eviction", "possession of weapons for unlawful purposes". Returns ranked sections with their citations (where parseable) and headings; use nj_statute_section afterward for the full text of one. Full-text search, so it answers questions no citation lookup can. Keyless.

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": "landlord grounds for eviction"
    },
    "name": "nj_statute_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25.
queryYesTopic or keywords, e.g. "security deposit interest". A few plain words works better than a long sentence — this engine ANDs every word.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive, so the safety bar is low. The description adds real context beyond them: the return shape ('ranked sections with their citations (where parseable) and headings'), that it is full-text, and that it is 'Keyless' (no auth setup needed). A minor gap is that ranking/recall behavior and result truncation are not described, keeping it from a 5.

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 and scope in the first clause, then return format, then the handoff, then a closing rationale. The three inline example queries add concrete meaning rather than filler, though the trailing 'answers questions no citation lookup can' is slightly redundant with the opening scope statement.

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?

There is no output schema, so the description must cover return values, which it does (ranked sections, citations where parseable, headings). With 100% parameter coverage in the schema and the follow-up sibling named, an agent has everything needed to call this correctly.

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 schema itself documents both parameters, including the default/max for limit and the AND-every-word behavior. The description's example queries and topic-vs-citation framing are useful semantics but largely reinforce what the schema already states, so the baseline of 3 applies.

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 (Search) and resource (New Jersey Statutes / N.J.S.A.) and sharply constrains the input mode: BY TOPIC or keyword rather than citation. The distinction from the sibling nj_statute_section is explicit, so an agent can route without opening either schema.

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?

Explicitly tells the agent when to use this tool (topic/keyword discovery, 'questions no citation lookup can') and names the follow-up alternative: 'use nj_statute_section afterward for the full text of one.' Coupled with a concrete example query, the routing is unambiguous.

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 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.

Resources