OpenVan MCP Server

Holidays And Peak Traffic Days

get_holidays

Read-onlyIdempotent

Retrieve public holidays, school holidays, and official peak traffic days for a country and date range up to 400 days. Use it to plan travel around days off and busy roads.

Instructions

Public holidays, school holidays (often regional, with ISO 3166-2 region codes) and official peak traffic days (France, Bison Futé) in one country for a period of up to 400 days. A country without data returns an error saying so — never present that as "no holidays". Use it for public holidays, days off, school holidays and peak traffic days.

Input Schema

Name	Required	Description
`to`	No	End of the period, YYYY-MM-DD. Defaults to from + 90 days; at most 400 days after from.
`from`	No	Start of the period, YYYY-MM-DD. Defaults to today.
`kind`	No	Only one kind: public holidays, school holidays (often regional), or traffic = official peak traffic days — France only (Bison Futé). For «when are the roads busy» elsewhere omit it: public and school holidays are the busy days. Omit for all.
`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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.9.7Oct 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / to / $ref
```
Removed value: -"#/properties/from"
```
- addedInput schema / properties / to / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
- addedInput schema / properties / to / type
```
Added value: +"string"
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed3 schema fields changedv0.6.4Oct 15, 2026

changedInput schema / properties / kind / description

Previous value: -"Only one kind: public holidays, school holidays (often regional), or traffic = official peak traffic days (France, Bison Futé). Omit for all."New value: +"Only one kind: public holidays, school holidays (often regional), or traffic = official peak traffic days — France only (Bison Futé). For «when are the roads busy» elsewhere omit it: public and school holidays are the busy days. Omit for all."

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

A4.2/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it warns that a country without data returns an error and must never be reported as 'no holidays', notes the 400-day cap, and flags that school holidays are often regional while traffic days are France-only. These are exactly the failure modes an agent would otherwise mishandle.

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?

Three sentences, front-loaded with scope, then the critical error caveat. The final sentence duplicates ground covered by the first and could be merged, but there is no padding beyond that.

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 described. Combined with annotations and full param coverage, the description supplies the remaining essentials: data-coverage failure semantics, the date-window limit, and the geographic restriction on traffic days.

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 explains country_code, from, to, kind and locale in detail. The description adds only the 400-day bound (already in the schema) and a passing mention of ISO 3166-2 region codes, so 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 resource set — public holidays, school holidays and official peak traffic days (Bison Futé) — scoped to one country over a period of up to 400 days. The scope and content are unambiguous and distinguish it from sibling tools like list_events or get_country_travel_brief.

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?

The closing sentence 'Use it for public holidays, days off, school holidays and peak traffic days' gives an intended-use list, but it largely restates the purpose line and names no alternative tool or exclusion condition relative to the ~29 siblings. Usage is implied rather than routed.

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