Bogeyland

rsvp_event

RSVP to a free event on this site (Wix Events). NOBODY IS ON THE GUEST LIST YET: a confirmation email goes to the address you provide, and the RSVP is only submitted when that person clicks the link (expires in 24 hours). Tell the user to check their inbox. Use a real address belonging to the person you are acting for — the confirmation link is deliberately not returned to you.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	The guest's own email — the confirmation link is sent here.
`lastName`	Yes	Guest last name.
`firstName`	Yes	Guest first name.
`event_slug`	Yes	Event slug from list_events.

TDQS

A5/5.0

Behavior5/5

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

Discloses key behaviors beyond the annotated fields: no guest list initially, email-based confirmation flow, RSVP only submitted on click, link expiration, and that the confirmation link is deliberately not returned. This is critical for a mutation tool with no 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?

Two tightly packed sentences plus one instruction. Every sentence adds value without redundancy. The main action is front-loaded, followed by critical caveats.

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 resulting flow (email sent, RSVP conditional on click). It clearly differentiates from sibling tools like 'reserve_event_tickets' and provides sufficient guidance 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.

Parameters5/5

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

Schema coverage is 100% and each parameter is described clearly. The description adds context (e.g., 'the guest's own email — the confirmation link is sent here') and specifies source for event_slug ('from list_events').

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 the tool's purpose: 'RSVP to a free event on this site (Wix Events).' It uses specific verbs and resource, and distinguishes from siblings like 'reserve_event_tickets' by specifying 'free event'.

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 when to use ('nobody is on the guest list yet'), what happens (confirmation email, link expires in 24 hours), and what to tell the user ('check their inbox'). Also advises to use a real address and notes that the confirmation link is not returned.

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?