Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Explore Leisure Activities & Things to Do

explore_leisure_activities
Read-onlyIdempotent

Recommends leisure activities, excursions, museums, parks, sports, workshops, cinema, and family spots for indoor, outdoor, or weekend plans.

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": {
      "city": "<city>"
    },
    "name": "explore_leisure_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name
limitNoMax recommendations (default 20, max 50)
localeNoPreferred language code (default: de)
settingNoFilter indoor (museums, cinema, theater, workshops) or outdoor (parks, landmarks, nature, sports)
audienceNoTarget audience filter
onlyFreeNo
dateOptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds nothing behavioral beyond that — it doesn't say whether city is mandatory for a meaningful result, how recommendations are sourced, or what happens when filters yield nothing.

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 dense sentence with the verb front-loaded and no filler. It reads as a category list rather than structured guidance, but nothing is wasted.

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

Completeness2/5

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

With 7 parameters (one required) and no output schema, the description should clarify how to combine filters and what the result set looks like; it does neither. The one-line scope statement leaves the agent guessing on filter strategy relative to many overlapping siblings.

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 coverage is 71%, with enums self-documenting setting, audience, locale, and dateOption. The description's mention of 'indoor, outdoor, or weekend' and 'family spots' loosely maps to setting/audience/dateOption but adds no syntax or selection guidance beyond the schema text.

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 (recommends) and resource (leisure activities) and enumerates concrete categories — museums, parks, sports, workshops, cinema, family spots — so the agent knows the content type immediately. However, it offers no differentiation from siblings such as discover_what_to_do or get_weekend_in_city, which plausibly overlap.

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?

The phrase 'for indoor, outdoor, or weekend plans' loosely signals the setting/dateOption filters but never states when to pick this tool over discover_what_to_do, search_places_and_pois, or get_weekend_in_city. No prerequisites, no exclusions, no alternatives are given.

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.