Skip to main content
Glama
Sign In
OpenVan MCP Server

OpenVan MCP Server

by openvancamp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check A License Plate

check_license_plate
Read-onlyIdempotent

Validate a license plate against a country’s format, normalize look-alike letters, and identify the region for its code. Check plate types without identifying the owner or vehicle location.

Instructions

Validate a plate number against the country's format (look-alike letters are normalized) and say which region its code belongs to. Pass type to check against a specific plate type's format. Never identifies the owner or the vehicle's location. Use it to check a specific plate number.

Input Schema

NameRequiredDescriptionDefault
typeNoPlate type key from get_license_plate_country, e.g. on Russian plates diplomatic (red), police (blue), military (black), taxi_bus (yellow). Default: the country's standard plate.
localeNoLanguage the user writes in (en, ru, de, fr, es, pt, tr). Set it on every call: the answer and the interactive card are shown in this language and units; without it the card falls back to the app's interface language.
numberYesPlate number without the region, e.g. A123BC. Look-alike Latin letters are normalized.
regionNoRegion code if the country shows one, e.g. 77.
countryYesISO 3166-1 alpha-2 country code, e.g. RU.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.7
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed2 schema fields changedv0.6.4
    • changedInput schema / properties / locale / description
      Previous value: -"Language of country and region names. Default en."New value: +"Language the user writes in (en, ru, de, fr, es, pt, tr). Set it on every call: the answer and the interactive card are shown in this language and units; without it the card falls back to the app's interface language."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
  3. Changed1 schema field changedv0.6.2
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Plate type key from get_license_plate_country, e.g. on Russian plates diplomatic (red), police (blue), military (black), taxi_bus (yellow). Default: the country's standard plate.",
+  "type": "string"
+}
  4. First observedv0.6.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: look-alike letter normalization, region-code inference, and a privacy boundary stating it never identifies the owner or vehicle location.

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?

The description is short, front-loaded, and covers the main behavior in the first sentence. The final sentence, "Use it to check a specific plate number," is somewhat redundant with the opening sentence.

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?

Given full schema coverage, an output schema, and complete annotations, the description adds the necessary remaining context: validation scope, normalization, region inference, type filtering, and privacy limits. Nothing critical for correct invocation is missing.

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 all five parameters are already documented in the schema. The description reinforces the type parameter's purpose and mentions normalization, but adds little beyond the schema's own parameter descriptions.

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?

The description uses a specific verb and resource: validate a plate number against a country format and identify the region code. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as get_license_plate_country or get_license_plate_image.

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?

It gives a clear use case: "Use it to check a specific plate number," and explains that the type parameter checks against a specific plate type's format. It does not explicitly name when not to use it or which sibling tool to choose instead.

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

Deploy Server

Other Tools