Skip to main content
Glama

Get a club or venue and its upcoming dates

get_venue_events
Read-onlyIdempotent

A club or venue by slug (from search_venues or search): address, facts and its upcoming parties.

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": {
      "slug": "<slug>"
    },
    "name": "get_venue_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe venue slug, e.g. berghain or rex-club.
localeNoLanguage of the texts and page links (default: en).

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 the response bundles venue facts with upcoming dates, which is useful, but says nothing about behavior for unknown slugs, empty event lists, or how the locale affects output beyond what the schema says.

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 no filler: resource, key, source of the key, and returned content. Slightly terse to the point of compressing the returned-payload detail into a trailing clause.

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?

There is no output schema, so the description carrying 'address, facts and its upcoming parties' is doing real work. For a lookup tool with a locale parameter and no output schema, though, it leaves gaps around locale-driven output and the shape/limits of the upcoming-dates list.

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 coverage is 100%, including an example slug and locale enum with default, so the schema does the heavy lifting. The description only reinforces that the slug identifies a club or venue; it adds no extra meaning for locale.

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 concrete verb+resource: fetches a club/venue by slug and returns address, facts, and upcoming parties. This distinguishes it from search_venues (which finds venues) by naming the lookup key and the payload, though it doesn't explicitly contrast with get_event or search_events.

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 parenthetical '(from search_venues or search)' tells the agent where the slug comes from, which is genuine precondition guidance. There is no explicit statement of when not to use it or how it differs from event-search siblings once a venue is known.

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.

Resources