Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Family & Kids Events

get_family_and_kids_events
Read-onlyIdempotent

Curated search specifically tailored for families, parents, and kids. Supports weather-proof indoor filtering.

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

Input Schema

NameRequiredDescriptionDefault
cityYesCity name
localeNoPreferred language code (default: de)
isIndoorOnlyNoFilter for indoor events (e.g. rainy day)

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 and openWorldHint=false, so safety is covered. The description adds the useful notion that results are "curated" and that indoor-only filtering supports weather-proof planning, but says nothing about result volume, ranking, or pagination.

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 short sentences with the audience scope front-loaded and the indoor-filtering capability second. It is efficient, though "specifically tailored" is mild marketing padding that could be tightened.

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 three-parameter read-only search with full schema coverage and no output schema, the description covers the basics. It is still thin on what makes results "curated" and how this differs from the general event search, which matters given the crowded sibling set.

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 city, locale, and isIndoorOnly are already fully documented. The description's mention of "weather-proof indoor filtering" merely restates the isIndoorOnly parameter rather than adding format, default, or edge-case detail.

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?

"Curated search specifically tailored for families, parents, and kids" states a specific search action and a clear audience/scope. It does not, however, distinguish this from the sibling search_events or explain what "curated" actually means in terms of results.

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 by the target audience (families, parents, kids); there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as search_events or get_weekend_in_city. An agent must infer that this is the family-oriented variant of a general event search.

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.