OpenVan MCP Server

Toll Road Rates By Country

get_toll_rates

Read-onlyIdempotent

Look up toll rates and vignette prices for one country using its ISO code. Get per-km fees by vehicle class, payment systems, concession sections, and toll bridges or tunnels.

Instructions

Toll reference for one country: payment system, per-km rates by vehicle class (car, campervan up to 3.5 t, over 3.5 t), vignette prices for every duration, concession sections and toll bridges/tunnels, each with verification date and source. Use it for toll roads, motorway fees, whether a vignette is needed and what it costs in one country.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.
`country_code`	Yes	ISO 3166-1 alpha-2 country code, e.g. FR.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.4Oct 15, 2026

changedInput schema / properties / locale / description

Previous value: -"Language of names: en, ru, de, fr, es, pt, tr."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"
+}

First observedv0.6.0Oct 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds useful content context (verification date and source per entry, vehicle classes) but says nothing about pagination, rate limits, or response structure beyond what the output schema likely provides.

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 resource and its contents, then usage. The long content enumeration is dense but each item adds informational value; no filler sentences.

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 exists so return-value explanation is unnecessary, and annotations cover safety. The description sufficiently conveys scope and content for a two-parameter read tool; only the relationship to the route-toll sibling is left implicit.

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 both country_code and locale are already well documented in the schema. The description implies country scoping and the vehicle-class dimension but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 resource (toll reference for one country) and enumerates concrete contents: payment system, per-km rates by vehicle class, vignette prices, concession sections, toll bridges/tunnels. It does not name or distinguish itself from the sibling estimate_route_tolls, which covers a closely related route-based use case.

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?

The second sentence gives clear context: use it for toll roads, motorway fees, and whether/at what cost a vignette is needed in one country. However, it never names the obvious alternative (estimate_route_tolls) or states when a per-route estimate is preferable, so there are no explicit exclusions.

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