Skip to main content
Glama

DOJO+

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.6/5.0
Behavior5/5

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

With no annotations, the description carries full burden and excels: discloses that booking is not finalized until payment, returns a checkout URL, the booking remains off-calendar, the email is not verified, and slot re-validation. This is rich, critical behavioral context beyond what a schema could convey.

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 moderately sized but every sentence carries essential information, from purpose to critical caveats to sequencing. It is slightly verbose but well-structured with clear emphasis on the payment caveat.

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?

Despite lacking an output schema, the description reveals the key return value (checkout URL), the off-calendar behavior, the prerequisite call to get_availability, and user instructions. This is sufficient for an agent to invoke the tool correctly and set user expectations.

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%, so baseline is 3. The description adds cross-tool context by referencing get_availability for start/end dates and list_booking_services for serviceId, which helps the agent correctly source parameter values. It also notes the contact email is not verified, adding behavioral nuance to the contact parameter.

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 via Wix Bookings, and immediately clarifies the crucial caveat that nothing is booked until payment. This distinguishes it from siblings like create_checkout by emphasizing the booking-creation aspect and the resulting checkout URL.

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

Usage Guidelines4/5

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

Provides strong when-to-use guidance: explicitly instructs to call get_availability immediately before and warns that a taken slot is rejected. It also tells to inform the user to open the link. However, it doesn't explicitly name alternatives or state when not to use the tool, leaving a minor gap.

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

All DOJO+ 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 targets a distinct resource or action (e.g., create_booking vs create_checkout, reserve_event_tickets vs rsvp_event), and descriptions provide clear boundaries. Even closely related tools like list_booking_services and list_pricing_plans are differentiated by context.

Naming Consistency5/5

All 26 tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, search_, etc.), with no mixed conventions or vague verbs. This makes the tool set predictable and easy to navigate.

Tool Count3/5

At 26 tools, the set is on the heavy side and exceeds the typical well-scoped range, but the diversity reflects a multi-featured directory covering bookings, events, store, reviews, forms, and more. Each tool appears to serve a distinct purpose, so the count is borderline rather than excessive.

Completeness4/5

The surface covers the core user workflows: search, view details, book services, reserve/RSVP events, request reservations, submit forms, and browse content. Minor gaps exist (e.g., no cancellation/update for bookings, no full blog post body), but these are workarounds and not critical for a consumer-facing directory.

Resources