OpenVan MCP Server

License Plate Image

get_license_plate_image

Read-onlyIdempotent

Draws an illustrative image of a country's standard civilian license plate from a country code and plate number, returning inline PNG 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

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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.9.7Oct 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real context beyond them: the response includes an inline PNG plus SVG/PNG links, and the number must conform to the country's standard format. It doesn't say what happens when the number is malformed or the country is unsupported, which keeps it below 5.

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?

Four short sentences, front-loaded with the core action and output format. The final sentence ('Use it to draw or show a picture of a plate') largely restates the opening, so not every sentence earns its place.

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?

Output schema and annotations carry return values and safety, and the description covers the drawing scope, exclusions and output links. It leaves open the failure behavior for invalid formats and doesn't clarify when region should be supplied, minor gaps for a two-required-parameter render tool.

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 that the number must match the country's standard format, which adds mild validation semantics, but it says nothing about the optional region parameter or the locale fallback behavior beyond what the schema already documents.

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 specific verb and resource: 'Draw an illustrative image of a country's standard civilian license plate', and names the output artifacts (inline PNG plus SVG/PNG links). It also scopes out official, police, military and diplomatic plates. It does not name the sibling check_license_plate or list_license_plate_countries to sharpen the distinction, so it falls short of a 5.

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 trigger, and 'Official, police, military and diplomatic plates are not drawn' provides an explicit when-not-to-use boundary. No alternative sibling is named for the excluded cases, so the routing guidance is incomplete.

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