Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Ticket Availability & Prices

get_event_tickets
Read-onlyIdempotent

Checks real-time ticket availability, tiers, prices, resale status on secondary fan market, box office availability, and direct ticket purchase links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "eventIdOrSlug": "<eventIdOrSlug>"
    },
    "name": "get_event_tickets"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoPreferred language code (default: de)
eventIdOrSlugYesThe event ID or slug to check tickets for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the data is real-time, spans primary tiers plus secondary fan-market resale and box-office channels, and includes purchase links. It does not discuss empty/availability-negative results, which would have made it a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the enumerations map directly to the value the tool returns. The list is somewhat dense but every item carries information about the response contents.

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 two-parameter, read-only lookup with no output schema, the description is rich enough about the kinds of ticket data returned. What remains unstated (behavior when no tickets exist, whether prices are guaranteed or cached) is minor for a read-only query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (eventIdOrSlug, locale enum with default 'de') are already fully documented in the schema. The description adds no additional meaning about parameter usage or the accepted ID/slug format, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Checks') with a specific resource ('ticket availability, tiers, prices, resale status... box office availability, and direct ticket purchase links'), so an agent knows exactly what data comes back. It does not name or contrast with the sibling 'find_tickets', so differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the required eventIdOrSlug signals this is for checking tickets on a known event. There is no explicit when-to-use/when-not-to-use guidance and no mention of how this differs from 'find_tickets' or 'get_event_details', which an agent would need to choose correctly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.