Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Search Viventii Events & Places

search_events
Read-onlyIdempotent

Searches events and local places on Viventii across cities, dates, categories, keywords, budgets, and accessibility. Always returns verified city hub URLs alongside matching listings.

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": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name (e.g. "Berlin", "Köln", "München", "Hamburg", "Frankfurt", "Bonn")
limitNoMaximum number of results (default 20, max 50)
queryNoFree text search (e.g. "techno open air", "indie concert", "jazz")
localeNoPreferred language code (default: de)
districtNoOptional city district or quarter (e.g. "Sachsenhausen", "Kreuzberg")
latitudeNoUser GPS latitude for proximity search
maxPriceNoMaximum ticket price in EUR
onlyFreeNoFilter for events with free admission
radiusKmNoProximity search radius in km (e.g. 15)
longitudeNoUser GPS longitude for proximity search
categoriesNoOptional categories (e.g. Music, Parties, Art, Food, Theater, Sports, Outdoors, Family, Shopping, Education, Fairs)
dateOptionNo
specificDateNoDate in European DD.MM.YYYY or ISO YYYY-MM-DD format
wheelchairOnlyNoFilter for 100% wheelchair-accessible venues

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond that - it always returns verified city hub URLs alongside listings - but says nothing about result ordering, pagination behavior, or what happens when zero filters are supplied.

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?

Two tight sentences with the capability front-loaded and the return guarantee second; nothing is redundant. Minor brand filler ("on Viventii") is the only wasted wording.

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?

For a 14-parameter tool with no output schema, the description covers the surface but not the operational details an agent needs - how filters combine, which are mutually exclusive (e.g. city vs latitude/longitude, dateOption=specific vs specificDate), and the default limit of 20. Annotations carry the safety story, so the gap is moderate rather than severe.

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 93%, so nearly every parameter is already documented in the schema, which sets the baseline at 3. The description's facet list (cities, dates, categories, keywords, budgets, accessibility) loosely maps onto the parameters but adds no format, default, or combination semantics beyond what the schema states.

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 ("Searches events and local places on Viventii") and enumerates the searchable dimensions (cities, dates, categories, keywords, budgets, accessibility). It is clear what the tool does, though the mention of "local places" slightly overlaps the sibling search_places_and_pois without clarifying the boundary.

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

Usage Guidelines2/5

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

Provides no when-to-use guidance and no exclusions or alternatives, despite siblings like get_tonight_in_city, get_weekend_in_city, discover_what_to_do and search_places_and_pois that plausibly compete for the same intent. The agent must infer that this is the general-purpose search versus the specialized time- or place-scoped tools.

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.