Skip to main content
Glama

Centro

by io.github.junoventures

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
NameRequiredDescriptionDefault
contactYesWho the booking is for. All three are required by the venue to confirm or reschedule.
endDateYesSlot end as an ISO instant, exactly as returned by get_availability.
serviceIdYesService ID from list_booking_services (called with the same place_slug).
startDateYesSlot start as an ISO instant, exactly as returned by get_availability.
place_slugYesVenue place slug from search_places.
resourceIdNoOptional staff/resource ID from the slot, when the user picked a specific professional.

TDQS

A4.7/5.0
Behavior5/5

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

Discloses key behaviors: payment required, returns checkout URL, slot re-validation server-side, email not verified, and potential slot rejection. No annotations exist, so description carries full burden and meets it well.

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?

Three sentences with critical warning front-loaded. All content is necessary, but slight room for further trimming without losing value. No redundancy.

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?

Covers purpose, prerequisites, post-steps, and behavioral limitations. No output schema, but mentions checkout URL. Lacks explicit return format, but acceptable given no output schema. Satisfies completeness for a complex 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%, baseline 3. Description adds value by referencing get_availability for date parameters, list_booking_services for serviceId, and clarifying contact fields are required by venue. Adds usage context beyond schema descriptions.

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?

Clear verb ('Book') and resource ('appointment slot at a venue') with explicit tie to Wix Bookings. Distinguishes from siblings by focusing on booking with payment flow.

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 states that nothing is booked until payment, requires calling get_availability immediately before, and instructs the agent to tell the user to open the link. Provides clear when-to-use and prerequisite.

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

All Centro toolsInspect
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.2/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose. Tools like create_booking and request_reservation target different services (appointments vs. restaurant tables), and reserve_event_tickets vs. rsvp_event differentiate paid holds from free RSVPs. No overlapping functionality that would confuse an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., create_booking, list_events, search_dishes) using lowercase with underscores. No mixing of conventions or irregular verbs.

Tool Count4/5

28 tools cover a broad domain of neighborhood directory services (bookings, events, movies, restaurant menus, forms, etc.). While the count is slightly high, each tool serves a specific function and is justified by the domain scope.

Completeness5/5

The tool set provides comprehensive coverage for a neighborhood directory: search, booking, reservations, event management, menus, reviews, forms, loyalty, and more. No obvious gaps; all core user needs are addressed.

Resources