Skip to main content
Glama

Itaim Bibi

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

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

With no annotations, the description fully bears the burden. It transparently reveals that nothing is booked until payment, it returns a checkout URL, and the contact email is not verified. No contradictions.

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?

The description is a single, concise paragraph that front-loads the purpose and follows with critical warnings. Every sentence adds value; no fluff.

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 no output schema, the description explains the return value (checkout URL) and the required pre-step (get_availability). It covers the complete workflow adequately.

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?

Schema description coverage is 100%, so the schema already explains all parameters. The description adds contextual value about the overall flow but does not add new parameter-specific details beyond the schema, resulting in a baseline score.

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 that the tool books an appointment slot at a venue (Wix Bookings), with a specific verb and resource. It distinguishes itself from sibling tools like get_availability and create_checkout.

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?

It explicitly instructs to call get_availability immediately before and explains that the slot is re-validated server-side. It also tells the user to inform the customer that payment must be completed. However, it does not explicitly mention when not to use it or compare with alternatives.

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

All Itaim Bibi 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: appointments, products, events, places, menus, reviews, forms, etc. No two tools have overlapping purposes; even similar booking tools (create_booking, request_reservation, reserve_event_tickets, rsvp_event) are clearly differentiated by description and use case.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase with underscores (e.g., create_booking, list_events, search_places). Verbs are appropriate (create, get, list, search, submit, request, reserve, rsvp) and nouns clearly indicate the resource.

Tool Count4/5

28 tools cover a broad domain (neighborhood directory with Wix integrations). While each tool has a clear purpose, the count exceeds the typical 3-15 range slightly, making the surface feel somewhat heavy but still manageable.

Completeness5/5

The tool surface provides comprehensive coverage for the domain: discovery (search places, list events, list guides), details (get place, get reviews), booking (appointments, restaurant, event tickets, RSVP), checkout, forms, FAQs, loyalty, pricing plans, and more. No obvious dead ends for common user journeys.

Resources