Reference

Documentation

Contracts, tool guides, data semantics, source rights, authentication, quotas, and known limitations.

Start here

search_melaka_places — Search covered Melaka demo or verified place facts with deterministic filters and evidence-aware matching. Use it to discover stable place IDs. Do not treat missing evidence as a passed hard constraint or use it for live inventory.
get_melaka_place_facts — Retrieve rights-filtered facts, field evidence, schedules, offers, services, facilities, and revisions for one covered place ID. Do not use it to confirm live operation, ticket inventory, or a booking.
check_melaka_visit_window — Check whether an arrival and duration fit published schedules, exceptions, last entry, and known service status. Use before finalizing an itinerary. This is not a real-time opening, inventory, or booking confirmation.
get_melaka_weather_advisory — Return the configured Melaka-area weather advisory state, forecast coverage, spatial granularity, validity, and evidence. Do not interpret area forecasts as venue conditions or absence of warnings as safety.
plan_melaka_day — Build a deterministic single-day candidate itinerary of at most eight stops from covered facts and explicit route assumptions. Use for a practical draft. It does not promise a globally optimal route or live availability.
validate_melaka_itinerary — Validate up to eight structured stops against published windows, services, costs, constraints, and supplied transport estimates. Use for an existing itinerary. Free-text parsing, booking, and live operation checks are not supported.

REST and Streamable HTTP MCP are implemented. ARD, A2A, OAuth, booking, inquiry, payment, and all other write actions are not enabled.