Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__nj_mvc_vehicle_inspections

Measure how often cars pass or fail New Jersey vehicle inspection, from the Motor Vehicle Commission's record-level results file, 2,314,032 individual tests, each carrying make, model, model year, fuel, and separate emissions and safety verdicts. Returns test counts with pass rate, fail rate, and how many failures were emissions rather than safety, grouped by make, model, model year, fuel, body style or test type. Answers "which cars fail NJ emissions inspection most", "Toyota Camry NJ inspectio

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": {
      "limit": 6,
      "group_by": "make"
    },
    "name": "nj-mvc__nj_mvc_vehicle_inspections"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelNoFuel; plain words map to New Jersey's codes, e.g. "gas" (GASO), "diesel" (DIES), "hybrid" (ELEG), "electric" (ELEC).
makeNoVehicle make, matched as a substring, e.g. "TOYOTA", "FORD", "HONDA".
sortNotests (default) ranks by volume; fail_rate ranks by the share of tests that failed.
limitNoMax groups to return (default 25, max 200).
modelNoVehicle model, matched as a substring, e.g. "CAMRY", "F150".
group_byNoBreakdown dimension: make, model, model_year, fuel, body_style, test_type, cylinders. Defaults to make.
min_testsNoDrop groups with fewer than this many tests before ranking, so a one-car model cannot top a failure-rate table. Default 100.
test_typeNoI for an initial test, R for a re-test. Defaults to every test.
model_yearNoFour-digit model year, e.g. "2015".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does substantial work: it names the source system, discloses the dataset size (2,314,032 tests), states that each record carries make/model/year/fuel plus separate emissions and safety verdicts, and specifies the returned measures (test counts, pass rate, fail rate, and the emissions-vs-safety failure split). It does not discuss read-only safety explicitly, pagination behavior, or response size limits, which keeps it below 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.

Conciseness3/5

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

The opening is front-loaded and information-dense, but the long enumeration of per-record fields is verbose for an aggregation tool, and the final sentence is truncated mid-phrase ('Toyota Camry NJ inspectio'), leaving a visible defect in the text. The valuable content survives, but the structure is not clean.

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?

For a nine-parameter aggregation tool with no output schema, the description explains what the response contains (counts, pass rate, fail rate, emissions failures) and the dimensions available for grouping, which is what an agent needs to compose a query. Only rate-limit and response-size behavior are unaddressed.

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% and all nine parameters are individually documented, so the schema already does the heavy lifting, including the fuel-code mapping and the min_tests rationale. The description adds only the conceptual framing of grouping and rate metrics, restating dimensions that already appear in the schema.

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?

The description pairs a specific verb ('Measure how often cars pass or fail') with a specific resource (NJ MVC record-level inspection results) and states the aggregation semantics: counts with pass/fail rates grouped by make, model, year, fuel, body style, or test type. That distinguishes it cleanly from the sibling nj_mvc_inspection_facilities, which concerns facilities rather than test outcomes.

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?

Usage is conveyed through concrete example questions ('which cars fail NJ emissions inspection most'), which tells the agent the analytical shape of request this tool serves. There is no explicit when-not-to-use guidance or named alternative for related questions, though the sibling set is mostly unrelated tools, so this gap is minor.

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.