Moema

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

Name	Required	Description
`contact`	Yes	Who the booking is for. All three are required by the venue to confirm or reschedule.
`endDate`	Yes	Slot end as an ISO instant, exactly as returned by get_availability.
`serviceId`	Yes	Service ID from list_booking_services (called with the same place_slug).
`startDate`	Yes	Slot start as an ISO instant, exactly as returned by get_availability.
`place_slug`	Yes	Venue place slug from search_places.
`resourceId`	No	Optional staff/resource ID from the slot, when the user picked a specific professional.

TDQS

A4.8/5.0

Behavior5/5

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

Discloses critical behaviors: booking stays off calendar until payment, slot re-validation, email not verified. Compensates fully for missing annotations.

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?

Single substantive paragraph with no redundancy. Every sentence adds essential information.

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?

Explains return behavior (checkout URL) despite no output schema. Could mention error handling, but overall complete for a booking 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%, but description adds value by explaining server-side re-validation and email verification context. Slight improvement over baseline.

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?

Clearly states it books an appointment slot at a venue via Wix Bookings. Distinguishes from siblings by emphasizing the checkout flow and payment requirement.

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 instructs to call get_availability immediately before, and explains that the booking is not confirmed until payment. Provides clear prerequisites and user guidance.

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

All Moema 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.2/5.0

Disambiguation5/5

Each tool targets a distinct resource and action (e.g., create_booking, create_checkout, request_reservation, reserve_event_tickets, rsvp_event all differ in purpose). Even similar-sounding tools like search_places and list_categories serve complementary roles (search vs taxonomy). No ambiguity.

Naming Consistency5/5

All 28 tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_blog_posts). No mixing of conventions or vague verbs.

Tool Count4/5

28 tools is above the typical 3-15 range but appropriate for the comprehensive scope of a neighborhood directory covering multiple Wix integrations (bookings, events, store, restaurants, etc.). Slightly heavy but well-scoped.

Completeness5/5

The tool surface covers the full lifecycle of a neighborhood directory: search, details, reviews, menus, booking, events, movies, offers, forms, FAQs, loyalty, etc. No obvious gaps; each domain has create/read/update/delete where applicable.

Resources

Need Help?