Bom Retiro

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.5/5.0

Behavior5/5

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

With no annotations, the description fully discloses key behaviors: no initial guest list, email-based confirmation with expiry, link not returned to caller. This gives the agent a complete understanding of the asynchronous flow.

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 (two main sentences plus an instruction), front-loaded with purpose, and every sentence earns its place. No unnecessary words.

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?

For a tool with 4 required params, no output schema, and no annotations, the description fully covers the behavioral nuances (email flow, expiry, user instruction) and parameter constraints. The agent has all needed information to use the tool correctly.

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

Parameters3/5

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

Schema coverage is 100% with good descriptions. The description adds value by reinforcing that the email must be the guest's own and that event_slug comes from list_events, but does not provide significant new detail beyond the schema.

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 verb 'RSVP' and the resource 'free event on this site (Wix Events)', distinguishing it from siblings like reserve_event_tickets (paid events) and create_booking (different domain).

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?

The description explains the workflow: confirmation email sent, RSVP only upon clicking, 24-hour expiry, and instructions to tell user to check inbox. It implies when to use (free events) but does not explicitly state when not to use or list alternatives.

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

All Bom Retiro 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 (bookings, store, events, restaurants, movies, etc.) with detailed descriptions that clearly differentiate their purposes. Overlap is minimal and handled by context, such as create_booking vs create_checkout vs request_reservation.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case, using prefixes like get_, list_, create_, search_, etc. The naming is predictable and makes it easy to infer the action and resource.

Tool Count4/5

28 tools is above the typical well-scoped range, but each tool covers a distinct feature of the neighborhood directory (places, events, movies, blog, forms, etc.). The count reflects the integration of multiple Wix apps, which is appropriate for a comprehensive directory.

Completeness4/5

The tool set covers most user-facing operations for a directory: search places, get details, book services, events, restaurant menus, etc. Minor gaps exist (e.g., no cancellation for bookings, no update operations), but these are likely out of scope for a public-facing server.

Resources

Need Help?