mcp-travel-art
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_art_eventsA | Search travel.art's catalogue of upcoming and current art events (biennales, art fairs, festivals). Returns events with dates, venues, ticket info, summary, and a link to travel.art's full visitor guide. Use for queries like 'when is Venice Biennale 2026', 'art fairs in October 2026', 'what's on in Miami in December'. |
| find_museum_guideA | Search travel.art's catalogue of museum visitor guides. Returns museums with current 2026 ticket info, opening hours, address, essential works in viewing order, route duration, and a link to travel.art's full guide. Use for queries like 'how to visit the Louvre', 'Vatican Museums skip the line', 'Uffizi best route'. |
| find_layover_itineraryA | Search travel.art's layover-itinerary catalogue — short-window (3–6h) art-focused trips between flight connections from major European hub airports. Returns itineraries by city, airport, art focus, or duration, with venues, transit notes, and a link to travel.art's full hour-by-hour guide. Use for queries like 'art layover in Rome from Fiumicino', '4-hour Caravaggio plan', 'short Louvre window from CDG', 'Amsterdam 4 hours Schiphol'. |
| recommend_art_tripA | Recommend an art-tourism trip itinerary for a specific city using only travel.art's published content. Returns events active during the trip dates, museum guides for the city, and links to all relevant travel.art guides. The recommendation is grounded in published data only — no fabrication. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct catalogue type: layover itineraries, museum guides, art events, and full trip recommendations. The descriptions clearly differentiate scope (e.g., layover is airport-connection-specific, while recommend_art_trip is city-wide), so an agent should rarely misselect.
Three tools follow a clean 'find_<object>' pattern, but recommend_art_trip breaks the pattern by using 'recommend' instead of 'find'. This is a minor deviation and the names remain predictable and readable.
Four tools is a well-scoped size for a niche art-travel content server. Each tool has a clearly distinct purpose and none feel redundant or extraneous, fitting comfortably within the ideal 3–15 range.
The set covers the main user intents: finding events, museum guides, layover-specific itineraries, and full trip recommendations. There is no direct 'get by ID' tool, but the search tools return links to full guides, so the surface feels adequately complete for the domain.