OpenVan MCP Server

Check Visa Rules

check_visa_rules

Read-onlyIdempotent

Get entry rules for a passport and destination: allowed stay, how days are counted, visa-run reset, and vehicle import — returned with a confidence level and source.

Instructions

Entry rules for one passport and destination: entry mode, allowed length of stay, how the days are counted (per entry or in a rolling window), whether a visa run resets the counter, and temporary vehicle import. Answers carry a confidence level and source — pass those on instead of stating a rule as certain.

Input Schema

Name	Required	Description
`plate`	No	Plate origin for the green card rule.
`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.
`weight`	No	Vehicle weight class for the vehicle rule: le35 (<=3.5 t) or gt35.
`passport`	Yes	ISO 3166-1 alpha-2 code of the passport, e.g. RU.
`destination`	Yes	Destination: ISO alpha-2 code, slug or zone code, e.g. TR.

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: +{}
```

Changed2 schema fields changedv0.6.4Oct 15, 2026

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

changedOutput schema / (root)

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

First observedv0.6.0Oct 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, open-world behavior, so the bar is lower. The description adds real value beyond them by disclosing that answers carry a confidence level and source and instructing the agent to propagate them rather than asserting rules as certain — a meaningful epistemic caveat not encoded anywhere in structured fields.

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?

Two sentences, front-loaded with the scope, then a distinct instruction about confidence/source. Dense but every clause earns its place by naming a returned dimension. The first sentence is long and list-heavy, but not wasteful.

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?

Given an output schema exists, the description needn't explain return shape, and annotations cover the safety profile. It fills the remaining gaps — the domains checked and the uncertainty/attribution requirement. The only missing element is disambiguation from sibling country/vehicle-rule tools.

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 schema already documents passport, destination, locale, plate, and weight in detail. The description adds only indirect hints — 'passport and destination' framing and the mention of 'temporary vehicle import,' which gestures at plate/weight — but never names or explains any parameter. Baseline 3 is appropriate.

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 (entry rules for one passport/destination) and enumerates exactly what is returned: entry mode, allowed stay length, day-counting method, visa-run reset behavior, and temporary vehicle import. It does not distinguish itself from close siblings such as get_route_visa_rules, get_customs_rules, or get_vehicle_import_rules, which is the only thing keeping it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'entry rules for one passport and destination' but there is no explicit when-to-use or when-not-use guidance, and no routing to alternatives. With siblings like get_route_visa_rules and get_vehicle_import_rules in the same family, an agent could easily pick the wrong one; the description gives no help there.

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