Skip to main content
Glama

Tatuapé

by io.github.junoventures
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
ticketsYesTicket types and quantities to hold.
event_slugYesEvent slug from list_events.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tickets / items / properties / pricingOptionId
      Added value: +{
+  "description": "Required when the ticket type lists pricingOptions in get_event_tickets: the id of the option the customer chose.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it states that the hold is temporary, nothing is paid, the tickets are not the user's until a human completes checkout, the hold expires automatically, and there are per-reservation limits. These are the critical behavioral traits an agent needs before calling the tool.

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 front-loaded with the core action and return value, then emphasizes the critical payment/hold warning. Every sentence adds useful information: the hold mechanics, quantity limits, and direct-sale restriction are all essential context.

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 having no annotations and no output schema, the description covers the essential behavior: what the tool does, the temporary nature of the hold, that payment occurs only after human checkout, the return value (checkout URL), quantity limits, and when the tool is not applicable. An agent can invoke it correctly with this information.

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 the schema already documents the parameters and baseline is 3. The description adds meaningful constraints not present in the schema: a maximum of 10 tickets and 10 ticket types per reservation, which helps an agent understand acceptable ticket array sizes.

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 states a specific action (hold tickets), resource (event tickets sold through this site), and outcome (returns a checkout URL). It also distinguishes this tool from handling externally sold events by pointing to the event's own ticketUrl, and the temporary-hold semantics separate it from payment or booking-finalization tools.

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?

It gives explicit conditions: use this only for events sold directly through Wix Events; for events sold elsewhere (Sympla, Ingresse, Sesc), use the event's own ticketUrl instead. It also explains the human checkout step and the temporary-hold consequence, leaving little ambiguity about when this tool applies.

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

All Tatuapé toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources