Bogeyland

reserve_event_tickets

Hold tickets for an event sold through this site (Wix Events) and return a checkout URL. THE HOLD IS TEMPORARY AND NOTHING IS PAID: the tickets are not the user's until a human opens the URL and completes checkout, and the hold expires on its own if they don't. Max 10 tickets and 10 ticket types per reservation. Only works for events this site sells directly — for events sold elsewhere (Sympla, Ingresse, Sesc), use the event's own ticketUrl instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tickets`	Yes	Ticket types and quantities to hold.
`event_slug`	Yes	Event slug from list_events.

TDQS

A4.8/5.0

Behavior5/5

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

Despite no annotations, the description fully discloses key behavioral traits: the hold is temporary, nothing is paid, tickets are not confirmed until checkout is completed, and the hold expires. Also mentions max limits of 10 tickets and 10 ticket types. This is comprehensive for a reservation tool.

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 concise (4 sentences), front-loaded with purpose, then critical behavioral info, constraints, and alternatives. Every sentence adds value with no redundancy.

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?

With no output schema, the description explains that a checkout URL is returned and that the hold process is temporary. It covers constraints and alternatives. It could optionally mention error scenarios, but overall it is complete given the tool's simplicity.

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%, and the description adds additional constraints beyond the schema: max 10 tickets and 10 ticket types per reservation. While the schema documents the parameters, the description enriches understanding with these limits.

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 the tool holds tickets for an event sold through Wix Events and returns a checkout URL. It distinguishes from siblings by specifying that for events sold elsewhere, one should use the event's own ticketUrl instead. This provides a specific verb+resource and differentiates from related tools.

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 states when to use (for events sold through Wix Events) and when not to use (for events sold elsewhere like Sympla, Ingresse, Sesc), providing an alternative (use ticketUrl). This gives clear context and exclusions.

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?