Agenda SP

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

Behavior5/5

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

With no annotations provided, the description fully carries the burden. It discloses that the hold is temporary, expires on its own, and does not constitute payment. It also warns that tickets are not secured until a human completes checkout via the URL.

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, with the main purpose stated first, followed by essential behavioral notes and constraints. Every sentence provides critical information without redundancy.

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?

Despite no output schema, the description explains the return value (checkout URL) and covers all behavioral aspects (temporary hold, expiry, limits). It also references related tools (get_event_tickets, list_events) and distinguishes from sibling tools. The description is complete for the tool's complexity.

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 baseline is 3. The description adds value beyond the schema by specifying that the tickets array must not exceed 10 total tickets and 10 ticket types, which is a constraint not present in the schema. This enhances parameter semantics.

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 'Hold tickets', the resource 'event tickets for an event sold through this site (Wix Events)', and specifies the return of a checkout URL. It also distinguishes from events sold elsewhere, 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?

The description explicitly explains when to use this tool (for Wix Events tickets) and when not (for events sold via Sympla, Ingresse, Sesc, use the event's own ticketUrl). It also provides constraints (max 10 tickets and 10 ticket types) and behavioral details (temporary hold, expires, requires human checkout).

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

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

Disambiguation4/5

Tools are mostly distinct with clear descriptions. Some overlap in actions that require user to click a link (create_booking, create_checkout, request_reservation, etc.), but each targets a different domain (booking, store, restaurant, event tickets, RSVP). Minor ambiguity possible but descriptions clarify.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., create_booking, get_availability, search_places). No deviations or mixed conventions.

Tool Count4/5

28 tools is slightly high for a neighborhood directory, but each serves a specific function (search, booking, events, movies, offers, etc.). The scope justifies the count, though some tools like list_blog_posts and list_faqs might be considered niche.

Completeness4/5

The tool set covers search, place details, categories, menus, events, movies, offers, booking, and forms. Missing update/delete operations for places or user management, but these are likely out of scope for a read-only directory. Core queries and actions are well-supported.

Resources

Need Help?