Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Release Radar & New Event Drops

get_release_radar
Read-onlyIdempotent

Returns the newest event drops published on Viventii, with optional city, category, price type, and focus mode filters.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city filter
limitNoMax items (default 20, max 50)
localeNoPreferred language code (default: de)
categoryNoOptional category key filter
focusModeNoPrioritize freshly dropped releases
priceTypeNoFilter by free or paid events

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that results are the newest published drops, but says nothing about ordering guarantees, result volume, pagination, or what happens when filters match 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?

One front-loaded sentence that identifies the resource before listing filters, with no filler. Slightly under-specified rather than verbose, so conciseness itself is not the issue.

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 no output schema, the description is the only place to learn what comes back, and it says only 'newest event drops' — no shape, count, or ordering detail. Annotations and full schema coverage make it callable, but an agent cannot predict the response structure.

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 every parameter including limit, locale, and enums is already documented. The description restates city, category, price type, and focus mode but adds no new meaning (e.g., how focusMode changes ordering relative to default) and omits limit and locale entirely. Baseline 3 applies.

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 and resource ('Returns the newest event drops published on Viventii') and enumerates the filter dimensions, so the agent knows exactly what it retrieves. It does not distinguish itself from siblings like get_city_radar or get_tonight_in_city, which sound closely related.

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 'newest event drops' — the agent can infer this is for discovering recent releases rather than searching a specific event. There is no explicit when-to-use, when-not-to-use, or routing to a sibling such as get_city_radar for city-scoped browsing.

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.