Moema

get_availability

Get available time slots for a bookable service on a given date (Wix Bookings). Pass the serviceId from list_booking_services and a date in YYYY-MM-DD. Pass the same place_slug you used there — slot times are returned in the VENUE's timezone, which is not necessarily the directory's.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Date in YYYY-MM-DD format (e.g. "2026-06-25").
`serviceId`	Yes	Service ID from list_booking_services.
`place_slug`	No	Venue place slug — use the same one passed to list_booking_services.

TDQS

A4.4/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that slot times are returned in the venue's timezone (not necessarily directory's). Also hints at dependency on list_booking_services for serviceId and place_slug.

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?

Three concise sentences with no wasted words. Front-loaded with purpose, followed by parameter usage and a key behavioral note.

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?

Given no output schema and no annotations, description adequately covers purpose, parameters, and behavior (timezone). Lacks details on return format (e.g., array of time slots), but is sufficient for an agent to use correctly.

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 specifying 'from list_booking_services' for serviceId, confirming YYYY-MM-DD format for date, and emphasizing to use the same place_slug and noting its effect on timezone.

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?

Description clearly states 'Get available time slots for a bookable service on a given date', specifying the verb (get), resource (available time slots), and context (Wix Bookings). It distinguishes from sibling tools like create_booking by focusing on availability.

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 explicit instructions to pass serviceId from list_booking_services and date in YYYY-MM-DD. Advises using the same place_slug and notes timezone behavior. Does not explicitly state when not to use, but context implies it is for checking availability before creating a booking.

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?