OpenVan MCP Server

License Plate Image

get_license_plate_image

Read-onlyIdempotent

Draw a standard civilian license plate for any country using a valid number and region. Returns an illustrative PNG inline plus SVG/PNG links.

Instructions

Draw an illustrative image of a country's standard civilian license plate (PNG shown inline, plus SVG/PNG links). The number must match the country's standard format. Official, police, military and diplomatic plates are not drawn. Use it to draw or show a picture of a plate.

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	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.
`number`	Yes	Plate number without the region, in the country's standard format.
`region`	No	Region code if the country shows one.
`country`	Yes	ISO 3166-1 alpha-2 country code, e.g. RU.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.6.4Oct 15, 2026

removedInput schema / properties / custom

Removed value: -{
-  "description": "Draw any text (e.g. a name) in the plate layout instead of requiring a real format.",
-  "type": "boolean"
-}

addedInput schema / properties / locale

Added value: +{
+  "description": "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.",
+  "enum": [
+    "en",
+    "ru",
+    "de",
+    "fr",
+    "es",
+    "pt",
+    "tr"
+  ],
+  "type": "string"
+}

changedInput schema / properties / number / description

Previous value: -"Plate number without the region, or any text with custom=true."New value: +"Plate number without the region, in the country's standard format."

removedInput schema / properties / type

Removed 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"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

Changed1 schema field changedv0.6.2Oct 5, 2026

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"
+}

First observedv0.6.0Oct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive profile, so the description only needs to add context — and it does: output is an inline PNG plus SVG/PNG links, the number must match the country's standard format, and several plate classes are refused. No auth, rate-limit, or failure behavior is described, but for a stateless rendering tool that is minor.

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?

Three short front-loaded sentences with no filler; the scope restriction appears before the closing usage line. The final sentence ('Use it to draw or show a picture of a plate') partially restates the opening, costing a little tightness.

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 an output schema present, return values need not be explained, and all four parameters are fully described in the schema. The description covers scope, format constraint, and output media; only error behavior for a malformed/invalid plate number is left unspecified.

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 the baseline is 3. The description reinforces the 'number' constraint ('must match the country's standard format') but adds nothing about region handling or the locale parameter, which the schema already documents thoroughly.

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 and resource ('Draw an illustrative image of a country's standard civilian license plate') and immediately scopes it to civilian standard plates, excluding official, police, military and diplomatic ones. This separates it cleanly from siblings like check_license_plate (validation) and get_license_plate_country (metadata).

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?

'Use it to draw or show a picture of a plate' gives a clear positive trigger, and the official/police/military/diplomatic exclusion defines when-not for plate categories. However, it never names the alternative tools (check_license_plate, list_license_plate_countries) an agent might confuse this with, so routing still requires inference.

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