Olé Futebol

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

A5/5.0

Behavior5/5

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

Despite no annotations, the description fully discloses behavior: nothing is booked until payment, returns a checkout URL, booking stays off calendar, server-side slot re-validation, and email not verified. No hidden behaviors.

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?

All sentences are substantive and well-organized: upfront purpose, critical warning in caps, usage prerequisites, and parameter hints. No fluff; each line earns its place.

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?

For a complex tool with 6 parameters, nested objects, no output schema, and important side effects, the description covers the entire flow: preconditions, behavior, post-conditions, and user action required. It is complete for effective use.

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

Parameters5/5

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

Schema coverage is 100%, but description adds valuable context: ties startDate/endDate to get_availability, serviceId to list_booking_services, place_slug to search_places, and explains contact requirements. This greatly aids parameter selection.

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?

Description clearly states the verb 'Book an appointment slot at a venue (Wix Bookings)'. It distinguishes from siblings by emphasizing that nothing is booked until payment, which sets it apart from tools like request_reservation or get_availability.

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 instructions: call get_availability immediately before, inform user about the checkout URL, and notes that contact email is not verified. It also warns about slot re-validation and rejection, covering when and how to use.

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

All Olé Futebol 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 resource or action (booking, checkout, availability, events, reviews, etc.). Even similar-looking tools like create_booking, request_reservation, and rsvp_event are clearly differentiated by their descriptions and target systems.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_booking_services). No mixing of conventions or unclear verbs.

Tool Count4/5

28 tools is on the higher end, but the server covers a wide domain (places, events, movies, booking, forms, loyalty, etc.). Each tool serves a clear purpose, so the count is justifiable, though minor trimming could be considered.

Completeness4/5

The tool set covers most workflows for a neighborhood directory: search, details, booking, events, reviews, etc. Some CRUD operations are missing (no update/delete for bookings), but these are consumer-facing actions where that is acceptable. The domain is well-covered.

Resources

Need Help?