OpenVan MCP Server

Travel Hazards In A Country

get_travel_hazards

Read-onlyIdempotent

Check current UK FCDO travel advice and active GDACS natural disasters for a country to determine if travel is safe now; use for travel warnings or safety questions.

Instructions

Situation now in one country: UK FCDO travel advice level and current GDACS natural disasters (flood, earthquake, tropical cyclone, wildfire, drought, volcano) with alert level green/orange/red. Not a forecast. Use it when someone asks whether it is safe to go to a country now, about travel warnings or natural disasters.

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. TR.

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 the country name: 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.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description earns credit by disclosing the external data provenance (FCDO + GDACS), the alert-level scale, and importantly that this is a point-in-time snapshot rather than a forecast — a real behavioral constraint not captured by the annotations.

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?

Three compact clauses: scope and contents first, the freshness caveat second, usage triggers last. No filler and nothing repeated from the schema or annotations.

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-value details are not needed. Given the read-only, single-lookup nature of the tool and the annotation coverage of safety, the description supplies everything needed to select and call it correctly: source, scope, freshness semantics, and the alert scale.

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% and both parameters are well documented in the schema itself (country_code format, locale language/units behavior). The description adds nothing about either parameter, 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 and resource scoped to 'one country' and enumerates the two concrete data streams it returns (UK FCDO advisory level and GDACS disaster events with green/orange/red alert levels). This distinguishes it cleanly from siblings like get_country_travel_brief, get_active_fires, or get_country_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 Guidelines4/5

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

Gives explicit triggering intents ('whether it is safe to go to a country now', 'travel warnings or natural disasters') and a negative boundary ('Not a forecast'). It does not name a sibling to use instead for related needs (e.g. fire-specific or weather queries), so routing when this is the wrong choice is left partly to inference.

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