Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Discover What to Do ("Was ist los?")

discover_what_to_do
Read-onlyIdempotent

Answers open-ended questions like "Was ist los in [Stadt]?" or "Was kann ich heute / am Wochenende machen?" by combining mood/intent matching, event results, and curated Viventii city guide links.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name (optional if coordinates are provided)
moodNoDesired mood or vibe
limitNoMax items (default 15)
queryNoAdditional user interest or keyword
localeNoPreferred language code (default: de)
onlyFreeNoShow only free-admission events
timeframeNoTimeframe such as today, tonight, tomorrow, or weekend

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorldHint=false, so the safety profile is covered. The description does add real value by disclosing that the response blends mood matching, event results, and curated Viventii guide links rather than pure event data. It stops short of describing result volume, ranking, or fallback behavior when nothing matches.

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 sentence with the purpose front-loaded and the examples doing the work of scoping the tool. It is dense but every clause carries information; only the parenthetical German title is slightly redundant.

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?

With seven optional parameters, zero required, and no output schema, an agent can call this with an empty object, and the description does not say what that yields or what defaults apply beyond what the schema states. The composite return is hinted at but the shape of a 'discovery' answer remains underspecified for a tool this open-ended.

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 baseline is 3, but the description goes slightly further by showing how free-text intent maps onto the mood and timeframe parameters ('heute', 'am Wochenende', 'in [Stadt]'). It still does not explain how query and mood interact or how limit applies across the combined result set.

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 gives a concrete verb-plus-resource framing ('answers open-ended questions') and illustrates it with two natural user phrasings, then states the composite nature of the result (mood/intent matching + event results + curated city guide links). This separates it in spirit from a plain event search, though it never names a sibling to sharpen the contrast.

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?

The example questions imply the use case is vague, conversational 'what's on' queries rather than structured lookups, which is useful inference. However, there is no explicit when-to-use vs. when-not, and no pointer to search_events, get_tonight_in_city, or get_weekend_in_city for more targeted needs.

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.