Bom Retiro

create_booking

Book an appointment slot at a venue (Wix Bookings). NOTHING IS BOOKED UNTIL THE CUSTOMER PAYS: this returns a checkout URL, and the booking stays off the venue's calendar until a human opens that URL and completes payment on the venue's own site. Tell the user they must open the link. Call get_availability immediately before this — the slot is re-validated server-side and a taken slot is rejected. The contact email is NOT verified at this step; the checkout is what confirms it.

Input Schema

TableJSON Schema

Name	Required	Description
`contact`	Yes	Who the booking is for. All three are required by the venue to confirm or reschedule.
`endDate`	Yes	Slot end as an ISO instant, exactly as returned by get_availability.
`serviceId`	Yes	Service ID from list_booking_services (called with the same place_slug).
`startDate`	Yes	Slot start as an ISO instant, exactly as returned by get_availability.
`place_slug`	Yes	Venue place slug from search_places.
`resourceId`	No	Optional staff/resource ID from the slot, when the user picked a specific professional.

TDQS

A4.8/5.0

Behavior5/5

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

No annotations provided, but the description fully discloses key behaviors: returns a checkout URL, nothing is booked until payment, slot re-validation, and lack of email verification.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the critical warning about payment and is well-structured, though it could be slightly more concise.

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 no output schema, the description explains the return value (checkout URL) and the overall flow, making it complete for a booking tool.

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?

Schema coverage is 100%, and the description adds context beyond the schema (e.g., slot times must match get_availability exactly, contact email not verified), which helps the agent.

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 books an appointment slot at a venue and distinguishes it from siblings by explicitly referencing get_availability as a prerequisite.

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 guidance: call get_availability before, inform user about the checkout URL, and notes that contact email is not verified until payment.

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?