Paraíso

get_availability

Get available time slots for a bookable service on a given date (Wix Bookings). Pass the serviceId from list_booking_services and a date in YYYY-MM-DD. Pass the same place_slug you used there — slot times are returned in the VENUE's timezone, which is not necessarily the directory's.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Date in YYYY-MM-DD format (e.g. "2026-06-25").
`serviceId`	Yes	Service ID from list_booking_services.
`place_slug`	No	Venue place slug — use the same one passed to list_booking_services.

TDQS

B3.4/5.0

Behavior3/5

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

The description discloses a behavioral trait: slot times are in the venue's timezone, not the directory's. With no annotations provided, the description carries full burden. It lacks details on side effects (likely read-only), handling of unavailable slots, or response structure, but the timezone note is valuable.

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 three sentences, front-loaded with the main action, and efficient. It avoids redundancy but could be slightly more structured (e.g., listing parameters). Still, every sentence adds value.

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

Completeness3/5

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

No output schema exists, so the description should clarify return format. It mentions 'available time slots' but not structure, pagination, or error cases. Given the tool's simplicity (3 params, no nested objects), the description is adequate but not fully complete.

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

Parameters3/5

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

Input schema coverage is 100%, so each parameter already has a description. The tool description adds little new: it reinforces the relationship to list_booking_services and place_slug, but doesn't add semantics beyond what the schema provides. Baseline is 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get available time slots for a bookable service on a given date'. It specifies the domain (Wix Bookings) and distinguishes from siblings like list_booking_services by referencing it as a prerequisite. However, it does not explicitly differentiate from other time-related tools like get_showtimes or get_event_tickets, which are also siblings.

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

Usage Guidelines3/5

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

The description provides usage instructions: pass serviceId from list_booking_services, a date in YYYY-MM-DD, and the same place_slug. It also warns about timezone behavior. However, it does not state when NOT to use this tool (e.g., if the service is not bookable) or suggest alternatives among siblings, leaving some ambiguity.

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

All Paraíso 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 (booking, store checkout, events, restaurant, etc.) with clear descriptions. No two tools have overlapping purposes; even similar actions like create_booking, create_checkout, and reserve_event_tickets are differentiated by their specific contexts.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with underscores (e.g., get_availability, list_blog_posts, reserve_event_tickets). There is no mixing of conventions like camelCase, and verbs are predictable (get, list, create, search, submit, etc.).

Tool Count4/5

With 28 tools, the count is slightly on the high side but justified by the broad scope covering a neighborhood directory with multiple features (places, events, movies, menus, bookings, forms, etc.). Each tool serves a clear purpose, though a few could be consolidated.

Completeness4/5

The tool surface is comprehensive for the server's purpose, covering search, details, bookings, events, movies, menus, blogs, FAQs, forms, and more. Minor gaps exist (e.g., no tool to cancel bookings or update reviews), but core workflows are well-covered.

Resources

Need Help?