Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__nj_mvc_inspection_facilities

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 repai

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": {
      "county": "Morris"
    },
    "name": "nj-mvc__nj_mvc_inspection_facilities"
  }
}

Input 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

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the whole behavioral burden. It does disclose provenance (MVC registry) and geographic scope (NJ only) and lists the returned fields, but says nothing about whether the call is read-only, how limit truncation interacts with a broader query, or anything about pagination or access requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, which is good, but the rest is a single run-on sentence of stacked clauses ending in a visibly truncated example ("emission repai"). The truncation and density cost it clarity.

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 no output schema, the description usefully enumerates the returned fields (name, address, town, phone, licence id, inspection capability), and the schema fully documents all seven optional filters. What is missing is whether the tool can be called with no filters and what the default result set then looks like.

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 every parameter already carries its own description, including matching behavior and the county-mislabeling caveat. The description's example values echo rather than extend those semantics, so the baseline 3 applies.

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 concrete verb and resource — find licensed NJ inspection / emission-repair facilities in the MVC registry — and enumerates the categories (private, state, emission repair) plus returned fields. It never contrasts itself with the sibling nj_mvc_vehicle_inspections, which sounds adjacent, so it stops short of full sibling differentiation.

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?

The embedded natural-language queries ("where can I get my car inspected in Edison NJ", "NJ diesel inspection station near ZIP 07740") make the intended use case concrete and easy to pattern-match against a user request. There are no explicit exclusions or named alternatives, so it is context rather than routing 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.