Moema

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

A4.7/5.0

Behavior5/5

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

Discloses key behaviors: confirmation email goes to provided address, RSVP only submitted when link clicked (24h expiry), link not returned to caller. No annotations, so description carries full burden and does so thoroughly.

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 sentences, front-loaded with purpose, then behavioral details. No fluff, every sentence adds value.

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?

Given no output schema and 4 parameters, description fully covers what the tool does, its side effects (email, expiry), and usage instructions. No apparent gaps.

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 meaning: email is 'the guest's own email', event_slug comes from list_events. Provides context beyond basic schema descriptions.

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 RSVPs to a free event, distinguishing it from siblings like reserve_event_tickets (which likely involves payments). Uses specific verb+resource: 'RSVP to a 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit context: 'NOBODY IS ON THE GUEST LIST YET', instructs to tell user to check inbox, and to use a real address. Could mention when to use alternatives like reserve_event_tickets, but the context is clear.

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?