Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Tonight Events in City

get_tonight_in_city
Read-onlyIdempotent

Fast radar for tonight in a city using Europe/Berlin local time (18:00 - 06:00 nightlife cycle, including ongoing late-night events after midnight).

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_tonight_in_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name (e.g. "Berlin", "Köln", "Frankfurt")
localeNoPreferred language code (default: de)
districtNoOptional district

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real behavioral content the annotations cannot: the Europe/Berlin timezone basis and the non-obvious rule that after-midnight events still count as 'tonight'. It still says nothing about result ordering, limits, or empty-result behavior.

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 the critical time window stated up front and no redundant restatement of the name. 'Fast radar' is the one phrase that reads as filler rather than specification.

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 only 3 fully documented parameters and no output schema, the description's main obligation is the temporal semantics, which it satisfies. It leaves open what the response contains (event summaries? tickets?) and whether the paywalled/nightlife scope has any limits, so an agent is only minimally equipped.

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%, including the locale enum and its de default, so the schema already carries parameter meaning. The description adds the time-filtering semantics that contextualize results but explains nothing about how city, district, or locale affect the query. Baseline 3 is correct.

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?

Names a specific resource (tonight's events in a city) and pins down the exact time window that defines 'tonight', which is the key scope distinction from get_weekend_in_city. 'Fast radar' is a bit marketing-flavored rather than a precise verb like 'list' or 'find', and no sibling is named explicitly, so it stops short of a 5.

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 18:00-06:00 nightlife window strongly implies when to call it, but the description never states when not to use it or routes the agent to alternatives such as get_weekend_in_city or get_city_radar. Usage is inferable rather than stated.

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.