Skip to main content
Glama
alexzavialov

mcp-travel-art

by alexzavialov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

find_art_events

Search upcoming and current art events by date, country, or type to get dates, venues, ticket info, and visitor guides.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by event type. Optional.
queryNoFree-text query (event name, theme, keyword). Optional.
countryNoISO 3166-1 alpha-2 country code (e.g., 'IT', 'CH', 'GB', 'US'). Optional filter.
activeOnNoISO 8601 date (YYYY-MM-DD). Returns only events whose date range covers this date. Optional.
endsBeforeNoISO 8601 date. Returns only events ending on or before this date. Optional.
startsAfterNoISO 8601 date. Returns only events starting on or after this date. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "biennale",
-  "art-fair",
-  "festival"
-]New value: +[
+  "biennale",
+  "art-fair",
+  "festival",
+  "museum-exhibition"
+]
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates that the tool is read-only ('Search', 'Returns'), scopes the data source ('travel.art's catalogue'), and describes what is returned (dates, venues, ticket info, summary, link). It does not mention edge behaviors like pagination or no-result handling, but the essential behavior is transparent.

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?

The description is two sentences plus example queries. It is front-loaded with the primary purpose, then lists return contents, then provides usage examples. Every sentence earns its place with zero redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 0 required parameters and no output schema, but the description adequately covers what the tool returns (dates, venues, ticket info, summary, link) and provides clear usage examples. It could mention default sorting or behavior without filters, but for a search tool this is sufficient.

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?

The schema descriptions cover 100% of the parameters, each with a clear explanation (e.g., 'ISO 8601 date (YYYY-MM-DD). Returns only events whose date range covers this date'). The description adds context through example queries but does not add parameter-specific nuances beyond what the schema already provides, warranting the baseline score.

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?

The description opens with 'Search travel.art's catalogue of upcoming and current art events', which clearly identifies the verb (Search), resource (catalogue of art events), and scope (travel.art). It also enumerates event types ('biennales, art fairs, festivals') and distinguishes itself from sibling tools like find_museum_guide and recommend_art_trip by focusing specifically on events.

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?

The description provides explicit example queries ('when is Venice Biennale 2026', 'art fairs in October 2026', 'what's on in Miami in December'), giving clear context for when to use the tool. However, it does not explicitly state when not to use it or mention alternatives by name, stopping short of a full 'when/when-not' guideline.

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

Deploy Server

Other Tools