Skip to main content
Glama

New Jersey MVC

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Nj Mvc Inspection Facilities

nj_mvc_inspection_facilities
Read-onlyIdempotent

Find a licensed New Jersey vehicle inspection or emission-repair facility — the private inspection stations, state inspection stations and registered emission repair shops overseen by the New Jersey Motor Vehicle Commission (MVC), the agency other states call the DMV. Returns the business name, street address, town, phone, licence id and whether it inspects cars, diesel or both. Answers "where can I get my car inspected in Edison NJ", "NJ diesel inspection station near ZIP 07740", "emission repair facility in Monmouth County", and "how many private inspection facilities does New Jersey license". Covers all 1,167 licensed facilities. For a driver license, ID card or registration renewal, the MVC runs separate licensing agencies that this file leaves out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoFive-digit New Jersey ZIP code, or a prefix, e.g. "07740" or "077".
cityNoTown name, matched as a substring, e.g. "Edison", "Long Branch". More reliable than county.
nameNoBusiness-name substring, e.g. "MIDAS", "AUTO".
limitNoMax facilities to return (default 50, max 200).
countyNoCounty name, e.g. "Morris", "Monmouth". Upstream mislabels some rows — prefer city.
facility_typeNoFacility category: "Private Inspection Facility", "Emission Repair Facility", "State Inspection Facility", "State Specialty Inspection Facility". Substrings such as "private" or "emission" also work.
inspection_typeNoWhat the shop inspects: "Auto Only", "Emission Repair Only", "Diesel Only", "Auto and Diesel". "diesel" alone matches both diesel categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds value by specifying the exact count of facilities (1,167) and listing returned fields. No contradictions. Does not mention rate limits, but annotations cover the essential behavioral traits.

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?

Single, well-structured paragraph. Front-loaded with purpose, then data returned, examples, coverage, and exclusions. Every sentence serves a distinct informative purpose; no redundancy.

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?

With 7 optional parameters and no output schema, the description provides sufficient context via examples and scope. It clarifies the exact coverage (1,167 facilities) and what is excluded. Could mention pagination or default limit, but the input schema covers 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 description coverage is 100%, so baseline is 3. The description does not add new parameter-level detail beyond the schema, though it provides example queries that illustrate parameter use. No additional depth is needed given the schema's thoroughness.

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?

Description clearly states the tool finds licensed NJ vehicle inspection/emission-repair facilities, lists returned fields, and gives example queries. It explicitly distinguishes from sibling tools by stating what it does not cover (driver license, ID card, registration renewals).

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 clear context on when to use (finding inspection facilities) and what to exclude (other MVC services). Offers example queries. Does not explicitly compare to the sibling 'nj_mvc_vehicle_inspections', but the exclusion statement serves as functional guidance.

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

All New Jersey MVC 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