Bogeyland

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

A5/5.0

Behavior5/5

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

Discloses critical behaviors beyond the tool's name: returns a checkout URL, booking stays off calendar until payment, contact email is not verified. No annotations exist, so description carries full burden and does so thoroughly. 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?

Five sentences, each essential and front-loaded with the key caveat about payment. No fluff, every sentence adds crucial information for correct invocation and user communication.

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, description explains return value (checkout URL). Covers preconditions (call get_availability), side effects (off calendar), and verification (email not verified). Adequately complete for a multi-step booking tool with payment dependency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 6 parameters are already described in schema (100% coverage). Description adds value: explains contact fields format and purpose (required to confirm), emphasizes start/end dates must be 'exactly as returned by get_availability', links serviceId to list_booking_services, place_slug to search_places, and resourceId optional for specific professional.

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 it books an appointment slot at a venue via Wix Bookings. The verb 'book' and resource 'venue' are specific. It distinguishes from siblings like get_availability (which must be called before) and request_reservation by highlighting the 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, notes that slot is re-validated and can be rejected, and specifies that nothing is booked until payment. Provides clear when-to-use and what the agent must communicate to the user (open link). No alternative tools mentioned, but guidelines are comprehensive.

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

All Bogeyland 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/5.0

Disambiguation5/5

Each tool targets a distinct domain (e.g., booking, restaurant reservation, event RSVP, movie showtimes) with clear descriptions that prevent confusion. Overlapping verbs like 'create' are used for different resource types, and the descriptions explicitly distinguish their contexts.

Naming Consistency5/5

All 28 tools follow a strict verb_noun pattern with underscores, e.g., create_booking, get_availability, list_events. No mixing of conventions or inconsistent verb styles.

Tool Count4/5

28 tools is at the upper end of reasonable for a broad neighborhood directory server covering places, bookings, events, movies, store, forms, and more. While each tool serves a distinct purpose, the count feels slightly high for a single server.

Completeness3/5

The tool surface covers core discovery and booking initiation (search, detail, book, reserve), but lacks lifecycle operations like cancel, update, or list user's existing bookings. Several operations require external checkout or confirmation links, creating workflow gaps.

Resources

Need Help?