OpenVan MCP Server

Estimate Tolls For A Route

estimate_route_tolls

Read-onlyIdempotent

Estimate toll costs for a road trip between 2-10 places. Returns a EUR range with per-country breakdown, including vignettes, bridges, and tunnels; flags missing data.

Instructions

Estimate toll cost for a road trip from 2-10 place names: per-km tolls, vignettes, bridges and tunnels, as a EUR range with a per-country breakdown. Flags partial results when a country on the route has no data. Use it only for the toll cost between named places when no other trip details are asked; for a whole trip use plan_road_trip.

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.
`waypoints`	Yes	2-10 place names in travel order: cities or countries (a country means its capital), e.g. ["Rome", "Paris"].
`vehicle_class`	No	car; van = campervan/motorhome up to 3.5 t (default); heavy = over 3.5 t.	van

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.4Oct 15, 2026

changedInput schema / properties / locale / description

Previous value: -"Language of bridge/section 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."

changedInput schema / properties / waypoints / description

Previous value: -"2-10 place names in travel order: cities, addresses or countries (a country means its capital), e.g. [\"Rome\", \"Paris\"]."New value: +"2-10 place names in travel order: cities or countries (a country means its capital), e.g. [\"Rome\", \"Paris\"]."

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

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: output is a EUR range with per-country breakdown, and it flags partial results when a country on the route lacks data—an important caveat an agent must surface to the user.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the core capability, then the routing rule and alternative. Every clause carries information; no filler.

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?

An output schema exists, yet the description still summarizes the return shape (EUR range, per-country breakdown, partial-result flags) and gives clear when-to-use routing. Nothing needed to call this correctly 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 coverage is 100%, so each parameter (locale, waypoints, vehicle_class) is already fully documented including enum meanings and defaults. The description's '2-10 place names' restates the schema's waypoint constraints but adds no format or unit detail beyond it, so the baseline 3 applies.

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 (estimate) and resource (toll cost) with precise scope: 2-10 place names, per-km tolls, vignettes, bridges/tunnels, EUR range with per-country breakdown. It is distinguishable from siblings like get_toll_rates (rates, not a route estimate) and plan_road_trip (whole-trip planning).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit routing guidance: 'Use it only for the toll cost between named places when no other trip details are asked; for a whole trip use plan_road_trip.' Both the inclusion condition and the named alternative are given.

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