Agenda Rio

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

Behavior5/5

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

Full disclosure of the double opt-in process: confirmation email, 24-hour expiry, link not returned. No annotations exist, so description carries full burden and meets it completely.

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 focused sentences plus an important caution. No filler, every sentence adds necessary behavioral context. Front-loaded with purpose.

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 complex confirmation flow, the description explains all key outcomes and user expectations. Agent can fully understand tool purpose and side effects.

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 covers 100% of parameters with descriptions. Description adds value by clarifying email is the guest's own and where confirmation is sent, and event_slug source. No contradictions.

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?

Clearly states 'RSVP to a free event' with specific resource (Wix Events) and process. Distinguishes from sibling tools like reserve_event_tickets by specifying free events and showing the double opt-in flow.

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: for free events, and explains that the guest must confirm via email. Tells user to check inbox and use real address. No misleading guidance.

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

All Agenda Rio 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

Every tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. Overlaps like create_booking vs request_reservation are clarified by domain (appointments vs restaurant) and mechanics.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., create_booking, list_events, search_places). The same conjugation style (snake_case) is used throughout, with no mixing of conventions.

Tool Count4/5

At 28 tools, the set is slightly larger than the typical well-scoped range (3-15), but each tool corresponds to a distinct feature of the neighborhood directory, making the count reasonable for the breadth of functionality.

Completeness5/5

The tool surface covers all major user-facing actions: searching, browsing, booking, purchasing, and retrieving information. No obvious gaps exist for the stated purpose of a neighborhood directory.

Resources

Need Help?