Agenda Rio

reserve_event_tickets

Hold tickets for an event sold through this site (Wix Events) and return a checkout URL. THE HOLD IS TEMPORARY AND NOTHING IS PAID: the tickets are not the user's until a human opens the URL and completes checkout, and the hold expires on its own if they don't. Max 10 tickets and 10 ticket types per reservation. Only works for events this site sells directly — for events sold elsewhere (Sympla, Ingresse, Sesc), use the event's own ticketUrl instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tickets`	Yes	Ticket types and quantities to hold.
`event_slug`	Yes	Event slug from list_events.

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses temporary nature, expiry, no payment, and limits. Could be more detailed on error handling, but overall transparent.

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?

Extremely concise: two sentences covering purpose, caveats, and exclusion. Front-loaded with the core action, no filler.

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?

For a simple tool with no output schema or annotations, the description covers key aspects: behavior, limits, and alternatives. Could mention return format, but not critical.

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%, so parameters are documented. The description adds context beyond schema (max limits, purpose of each parameter via example), providing meaningful additional guidance.

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 holds tickets and returns a checkout URL. It specifies the resource (Wix Events tickets) and distinguishes from external events, making the purpose unambiguous.

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 states when to use (Wix Events) and when not (external events, use their ticketUrl). Also provides constraints (max 10 tickets, 10 types) and clarifies the hold is temporary with no payment.

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?