Filipe Coffee

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

Behavior5/5

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

Despite no annotations, the description fully discloses the unusual behavior: no immediate RSVP, confirmation email sent, link click required, 24-hour expiry, and that the confirmation link is not returned. This exceeds expectations for non-annotated tools.

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 efficiently written, with each sentence adding necessary information: purpose, behavior, user instructions. No redundancy or irrelevant details.

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?

While the description covers the key behavioral aspects, it does not mention the immediate return value of the tool (likely a confirmation message). However, given the complexity and lack of output schema, it remains sufficiently informative.

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 descriptions cover parameters adequately (100% coverage), and the tool description adds significant context about the email parameter and the overall process, elevating understanding beyond schema alone.

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 action (RSVP), the resource (free event on Wix Events), and distinguishes it from other tools by specifying 'free event' which sets it apart from reserve_event_tickets for paid events.

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 provides clear context for use (free events) and specific instructions (tell user to check inbox, use real address), but does not explicitly mention when not to use or name alternative tools.

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

All Filipe Coffee 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.1/5.0

Disambiguation5/5

Each tool targets a distinct resource or action (e.g., bookings, events, places, menus, forms), with detailed descriptions that clearly differentiate even similar operations like create_booking vs. reserve_event_tickets. No two tools overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., create_booking, get_availability, list_events). Verbs are semantically appropriate (create, get, list, search, submit) and predictable.

Tool Count4/5

28 tools is slightly above the typical 3-15 range, but the breadth of the neighborhood directory domain justifies each tool. The count feels dense but not excessive, with no redundant tools.

Completeness5/5

The tool set covers the full lifecycle of a neighborhood directory: place search, restaurant menus, events, movie showtimes, booking, reviews, blog, guides, offers, loyalty, forms, and profiles. Obvious gaps like review creation are absent but likely out of scope.

Resources

Need Help?