openvan-travel

Countries With The Best Travel Weather

list_best_weather_countries

Read-onlyIdempotent

List the N countries where the weather is best for travelling by campervan, highest 0-100 travel score first: today's score by default, or with period=week the score of the coming 7 days (the ranking used on OpenVan.camp). Use it when no country is named and someone asks where to go for warm or good weather right now — worldwide or in a region (region=europe…); with sort=warmest only when they literally ask where it is warmest or hottest (it ranks by temperature alone, so deserts come first; «warm and pleasant», «warm and dry» → the default score). These are today's conditions and the coming days, not a forecast for a later month: for «in November» say so.

Input Schema

Name	Required	Description	Default
`sort`	No	score = best overall travel weather (default, also for «warm and pleasant»); warmest = highest daytime temperature today — only for a literal «where is it warmest/hottest».	score
`limit`	No	How many top-scoring countries to return.
`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.
`period`	No	today = today's score (default, «right now»); week = the score of the coming 7 days, the ranking used on OpenVan.camp — for «this week», «the coming days», «where to go next week».	today
`region`	No	Only countries of this region — «best weather in Europe». asia includes the Middle East; cis = Russia, the Caucasus and Central Asia. Default: world.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026

addedInput schema / properties / period

Added value: +{
+  "default": "today",
+  "description": "today = today's score (default, «right now»); week = the score of the coming 7 days, the ranking used on OpenVan.camp — for «this week», «the coming days», «where to go next week».",
+  "enum": [
+    "today",
+    "week"
+  ],
+  "type": "string"
+}

removedInput schema / properties / region / default
```
Removed value: -"world"
```

changedInput schema / properties / region / description

Previous value: -"Only countries of this region — «best weather in Europe». Default: world."New value: +"Only countries of this region — «best weather in Europe». asia includes the Middle East; cis = Russia, the Caucasus and Central Asia. Default: world."

changedInput schema / properties / region / enum

Previous value: -[
-  "world",
-  "europe",
-  "asia",
-  "africa",
-  "north_america",
-  "south_america",
-  "oceania"
-]New value: +[
+  "world",
+  "europe",
+  "asia",
+  "middle_east",
+  "cis",
+  "africa",
+  "north_america",
+  "south_america",
+  "oceania"
+]

Changed3 schema fields changedOct 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / limit / default
```
Removed value: -10
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
First observedOct 18, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent and open-world behavior, so the description doesn't need to restate safety. Instead it discloses the ranking semantics (0-100 score vs raw temperature), that results are today's/coming-days conditions rather than a later-month forecast, and that sort=warmest puts deserts first — behavior an agent could not infer from the schema.

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?

Front-loaded with the core action and ranking order before the conditions. It is a single dense run-on paragraph with several nested parentheticals, which costs a little readability, but every clause carries a real decision rule rather than 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?

Output schema exists, so return values needn't be explained, and annotations cover safety. What remains — when to call, how the ranking differs from raw temperature, and the temporal scope — is all present, leaving nothing an agent needs missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and enums are documented, so the baseline is 3. The description still adds decision rules the schema only partially carries, notably the disambiguation between sort=warmest and the default score and the '«in November» say so' caveat for period.

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?

Starts with a specific verb and resource: 'List the N countries where the weather is best for travelling by campervan, highest 0-100 travel score first.' It also names the ranking source (OpenVan.camp), which separates it from the per-country/per-city siblings like get_country_travel_weather or get_city_travel_weather.

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?

Gives an explicit trigger ('when no country is named and someone asks where to go'), an explicit alternative routing rule ('with sort=warmest only when they literally ask where it is warmest'), and the counter-case ('warm and pleasant' → default score). It also states a scope limit for future months, which tells the agent when not to use it as intended.

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

All openvan-travel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.