Bom Retiro

reserve_event_tickets

Hold tickets for an event sold through this site (Wix Events) and return a checkout URL. THE HOLD IS TEMPORARY AND NOTHING IS PAID: the tickets are not the user's until a human opens the URL and completes checkout, and the hold expires on its own if they don't. Max 10 tickets and 10 ticket types per reservation. Only works for events this site sells directly — for events sold elsewhere (Sympla, Ingresse, Sesc), use the event's own ticketUrl instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tickets`	Yes	Ticket types and quantities to hold.
`event_slug`	Yes	Event slug from list_events.

TDQS

A4.9/5.0

Behavior5/5

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

No annotations exist, so the description carries full burden. It discloses critical behaviors: the hold is temporary, non-paid, requires a human to complete checkout via URL, and expires automatically. This level of transparency is thorough for an agent.

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?

Two focused sentences with key information front-loaded, plus a concise third sentence for limitations and alternative. No redundant words.

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

Completeness5/5

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

Given the tool's simplicity (2 parameters, no output schema), the description covers purpose, behavior, constraints, and alternatives comprehensively. Return value is implied (checkout URL) sufficiently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% description coverage, providing baseline value. The description adds extra constraint (max 10 tickets and 10 ticket types) not in the schema, offering additional semantic guidance.

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 clearly states the tool holds tickets and returns a checkout URL for events sold through Wix Events, distinguishing it from sibling tools by specifying it only works for directly sold events and directing users to the event's own ticketUrl for external events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use (holding tickets for Wix Events) and when-not-to-use (events sold elsewhere), along with limits (max 10 tickets and ticket types) and the temporary nature of the hold.

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

All Bom Retiro tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool targets a distinct domain (bookings, store, events, restaurants, movies, etc.) with detailed descriptions that clearly differentiate their purposes. Overlap is minimal and handled by context, such as create_booking vs create_checkout vs request_reservation.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case, using prefixes like get_, list_, create_, search_, etc. The naming is predictable and makes it easy to infer the action and resource.

Tool Count4/5

28 tools is above the typical well-scoped range, but each tool covers a distinct feature of the neighborhood directory (places, events, movies, blog, forms, etc.). The count reflects the integration of multiple Wix apps, which is appropriate for a comprehensive directory.

Completeness4/5

The tool set covers most user-facing operations for a directory: search places, get details, book services, events, restaurant menus, etc. Minor gaps exist (e.g., no cancellation for bookings, no update operations), but these are likely out of scope for a public-facing server.

Resources

Need Help?