OpenVan MCP Server

Holidays And Peak Traffic Days

get_holidays

Read-onlyIdempotent

Retrieve public holidays, school holidays, and peak traffic days for a country over a period up to 400 days. Plan trips and days off with accurate data.

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

TableJSON 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

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 / 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/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description still adds the 400-day range limit and, importantly, the error-on-missing-data behavior that an agent must not misreport. This is genuine beyond-annotation context.

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 compact sentences with no filler, and the scope (three holiday kinds, one country, up to 400 days) is front-loaded before the error caveat. Slightly dense but every clause carries information.

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, so return-shape explanation is not needed. With annotations covering safety and the schema covering all five parameters at 100% coverage, the description supplies exactly the missing pieces: scope, the range limit, and the error-interpretation caveat.

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 from/to defaults, the 400-day cap, the kind enum, and locale. The description adds only the note that school holidays are often regional with ISO 3166-2 codes and that traffic days are France-only, which mostly duplicates the schema's kind description. 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?

The description names a specific resource set — public holidays, school holidays, and official peak traffic days — scoped to one country over a bounded period, which is unambiguous. It lacks an explicit verb framing and does not name a sibling, but no sibling tool covers holidays, so confusion risk is low.

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?

It states the use cases directly ("Use it for public holidays, days off, school holidays and peak traffic days") and gives an operational rule about error results — "never present that as 'no holidays'". It does not name a when-not case or a competing tool, but the guidance is concrete and actionable.

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