Get what's currently playing at festival/party events. Returns live stage information with current artists. Use this to answer 'What's on now?' or 'Who's playing right now at AYA?'
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | Filter by city | |
| event_id | No | Filter to specific event | |
| event_week_id | No | Filter to specific event week/festival |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It mentions returns live stage information but does not clarify how 'current' is determined (e.g., real-time vs schedule-based) or any side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-loading the core purpose and ending with example use cases. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity and no output schema, the description sufficiently explains return value (stage info, current artists). Sibling tools are listed for context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so parameters are well-documented. Description does not add additional semantics beyond the schema, meeting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States it gets what's currently playing at festival/party events with live stage info and current artists. Clearly differentiates from sibling tools like get_event_schedule.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly provides use cases: answering 'What's on now?' or 'Who's playing right now at AYA?'. Does not exclude any scenarios, but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resources and actions, such as get_artist vs get_artist_events and get_event_schedule vs get_now_playing. A few pairs like list_artists/search_artists and get_event_weeks/search_event_weeks could be confused, but their descriptions clarify browse vs search.
Tool names follow a consistent verb_noun pattern with get, list, and search. Minor inconsistency exists because get_ is used for both singular retrieval (get_artist) and collection listing (get_cities, get_event_weeks), while list_ only appears in list_artists. Overall predictable and readable.
16 tools is slightly above the typical 15-tool threshold but well-justified by the broad domain covering artists, events, venues, cities, event weeks, and organizers. Each tool serves a distinct purpose and none feel redundant.
The surface is comprehensive for a read-only events data API, covering artist browsing/search/details, event search/details/schedule/live, venue listing, city stats, event week management, and organizer search. Minor gaps include absent get_venue_details and get_organizer, but these can be derived from event details.