Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Active Cities Nightlife & Event Radar

get_city_radar
Read-onlyIdempotent

Overview of active cities on Viventii, popular genres, top venues, event counts, and curated direct city guide URLs.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city to focus on
localeNoPreferred language code (default: de)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/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 the safety profile is covered. The description contributes some useful context by disclosing the payload contents (event counts, curated city guide URLs), but says nothing about result size, ordering, or how the optional city/locale affect the aggregation.

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 no filler, and the content enumeration is front-loaded so the agent immediately sees what comes back. The lack of a leading verb makes it read as a label rather than a statement of action, which slightly weakens the structure.

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 zero-required-parameter read-only discovery tool with no output schema, describing the returned fields is genuinely helpful. But it omits how the two optional parameters shape the results and how this differs from the several overlapping discovery siblings, leaving a real gap for correct tool selection.

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 the schema fully documents both the optional city filter and the locale enum with its default. The description adds nothing beyond the schema — it only alludes to 'active cities' without explaining how the city parameter narrows or focuses the radar output. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (active cities overview) and enumerates what it contains — popular genres, top venues, event counts, curated city guide URLs — which is more than a restatement of the title. However, it is a bare noun phrase with no verb, and it does not distinguish this 'radar' feed from siblings with overlapping scope such as list_cities_and_categories or discover_what_to_do, so an agent cannot confidently tell them apart.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The agent must infer from the title alone whether this is a starting-point discovery call or a city listing, and cannot tell why it should be chosen over get_tonight_in_city or list_cities_and_categories.

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.