Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Weekend Events in City

get_weekend_in_city
Read-onlyIdempotent

Finds events and things to do this weekend (Friday to Sunday) in a specific city, with optional district or category filter and direct weekend hub links.

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

Input Schema

NameRequiredDescriptionDefault
cityYesCity name (e.g. "Berlin", "Köln", "München", "Bonn")
limitNoMax events to return (default 20)
localeNoPreferred language code (default: de)
categoryNoOptional category key (e.g. Music, Parties, Art, Food, Sports, Family)
districtNoOptional district
onlyFreeNoFilter for free weekend events only

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 the safety profile is fully covered elsewhere. The description adds only that results include 'direct weekend hub links', with no detail on pagination, result ordering, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no padding: the resource, the time window, and the optional filters in order of importance. Nothing here is redundant with the title or wasteful.

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

Completeness4/5

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

Six parameters but every one is documented in the schema, and annotations cover the read-only/idempotent profile, so little burden remains. The only real gap is return-shape detail beyond 'hub links', which is minor given there is no output schema.

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, limit, locale, category, district and onlyFree are all already documented in the schema. The description merely echoes that district/category filters exist and adds no syntax, default, or interaction meaning beyond the schema.

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?

Clear verb+resource ('Finds events and things to do') with an explicit scope: this weekend, defined as Friday to Sunday, in a named city. That time-window framing implicitly separates it from the sibling get_tonight_in_city, though the description never names the alternative outright.

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 weekend framing; an agent must infer that a user asking for 'plans this weekend' selects this and a user asking for 'tonight' does not. No explicit when-to-use, when-not-to-use, or named alternatives are provided.

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.