Paraíso

list_booking_services

List a venue's services — what it offers, with price and duration. Pass place_slug (from search_places) to list the services of a specific VENUE — a salon, clinic or studio listed in this directory; that is what you want in almost every case, and it is the only form whose serviceId works with create_booking. Omitting place_slug lists the directory site's own services instead, which most sites do not have. Returns name, description, price, duration in minutes, and bookableViaMcp. Services are listed for EVERY venue, including those with no online booking system — check bookableViaMcp: when it is false, id is null and you cannot book through create_booking, so point the user at bookingUrl or the venue's page instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`place_slug`	No	Venue place slug from search_places. Strongly recommended — without it you get the directory's own services, not a venue's.

TDQS

A4.6/5.0

Behavior4/5

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

No annotations provided, so description bears full burden. It discloses that services are returned for all venues, including those without online booking, and explains the bookableViaMcp flag and null id behavior. Lacks explicit mention of read-only nature but covers key behavioral traits.

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?

Well-structured with front-loaded purpose, followed by clarifications. Each sentence adds unique information without redundancy. Efficient use of space.

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

Completeness4/5

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

For a simple listing tool with one optional parameter and no output schema, the description adequately mentions key output fields (name, description, price, duration, bookableViaMcp) and handles the edge case of non-bookable venues. Could mention pagination or list format, but overall complete.

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%, baseline 3. The description adds value by explaining the dual behavior of place_slug, emphasizing it is strongly recommended, and linking serviceId usability with create_booking. This goes beyond the schema's parameter description.

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 it lists a venue's services with price and duration, and distinguishes between two modes (with or without place_slug). It uses the verb 'list' matching the tool name and effectively differentiates from sibling tools like create_booking and 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?

Explicitly tells when to use each mode: pass place_slug from search_places for venue services (usual case), omit for directory's own services (rare). Advises checking bookableViaMcp to handle non-bookable venues and mentions that only venue serviceId works with create_booking.

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?