Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Find Events with Online Tickets

find_tickets
Read-onlyIdempotent

Finds events with buyable online tickets (0% organizer fee Viventii ticketing or official ticket link) including prices and direct booking URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_tickets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name
limitNoMax ticketed events to return (default 20, max 50)
queryNoArtist, event name, or keyword
localeNoPreferred language code (default: de)
maxPriceNoMaximum ticket price in EUR
categoriesNo
dateOptionNo
specificDateNoDate in DD.MM.YYYY or YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered. The description adds real value by disclosing the eligibility rule (0% organizer fee Viventii ticketing or official link) and that results carry prices and direct booking URLs, but says nothing about what happens when no ticketed events exist or any rate/region limits.

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. The parenthetical is slightly dense but each clause (eligibility, prices, booking URLs) contributes information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Eight parameters, no output schema, and zero required parameters make this a fairly complex discovery tool; the description covers the return content in outline but omits how filters combine and any result-size behavior, leaving meaningful gaps.

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 75%, so most parameters are already documented in the schema. The description adds no parameter-level meaning (city, query, maxPrice, dateOption interplay are unmentioned), so it does not compensate for the remaining gap.

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?

States a specific verb and resource ('Finds events') plus the distinguishing filter: only events with buyable online tickets via Viventii ticketing or an official ticket link. That distinguishes it from generic event search, though it never names a sibling tool explicitly.

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?

Implied usage is clear (use when the user wants to actually purchase tickets rather than just browse events), but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as search_events or get_event_tickets.

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.