Get ticket types and prices for a specific event (Wix Events). Pass the event slug from list_events. Returns ticket names, prices, sale status, and how many are left.
| Name | Required | Description | Default |
|---|---|---|---|
| event_slug | Yes | Event slug from list_events. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose all behavioral traits. It mentions return fields (names, prices, sale status, quantity) but does not explicitly state that the operation is read-only or note any side effects, errors, or authentication needs.
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?
The description is two sentences, front-loading the purpose and then providing usage and return details. Every sentence adds value, with no unnecessary 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 (1 parameter, no output schema), the description covers purpose, parameter source, and return fields. It lacks error handling or edge case notes but is nearly complete for a straightforward read operation.
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% (the single parameter is documented). The description adds context that the slug comes from list_events, which is helpful but minimal. Baseline score of 3 is appropriate.
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?
The description clearly states the tool retrieves ticket types and prices for a specific event, with the verb 'Get' and resource 'ticket types and prices' for a 'specific event'. It distinguishes from siblings like reserve_event_tickets by focusing on read-only information.
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?
The description advises to 'Pass the event slug from list_events', providing clear prerequisite guidance. However, it does not explicitly contrast with alternative tools (e.g., reserve_event_tickets) or state when not to use this tool.
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.
Each tool has a clear, distinct purpose. Tools like create_booking and request_reservation target different services (appointments vs. restaurant tables), and reserve_event_tickets vs. rsvp_event differentiate paid holds from free RSVPs. No overlapping functionality that would confuse an agent.
All tool names follow a consistent verb_noun pattern (e.g., create_booking, list_events, search_dishes) using lowercase with underscores. No mixing of conventions or irregular verbs.
28 tools cover a broad domain of neighborhood directory services (bookings, events, movies, restaurant menus, forms, etc.). While the count is slightly high, each tool serves a specific function and is justified by the domain scope.
The tool set provides comprehensive coverage for a neighborhood directory: search, booking, reservations, event management, menus, reviews, forms, loyalty, and more. No obvious gaps; all core user needs are addressed.
