Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Event or Place Details

get_event_details
Read-onlyIdempotent

Provides the full profile of a specific event or place: description, lineup timetable, dresscode, age restrictions, door time, public transit, parking, iCal export link, and direct booking URLs without login redirect.

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": {
      "eventIdOrSlug": "<eventIdOrSlug>"
    },
    "name": "get_event_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoPreferred language code (default: de)
eventIdOrSlugYesThe event ID or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive lookup, so the description is not obligated to restate safety. It does add genuinely new behavior: the booking URLs are direct and skip login redirects, and the enumerated fields tell the agent what it will receive even though no output schema exists.

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 core purpose first and the field inventory second; nothing is redundant. The long enumeration is dense but each item carries real information for a tool with no output schema.

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?

With no output schema, describing the returned fields is the right compensation, and the description does that well for a two-parameter read tool. Minor gaps remain: it doesn't say how event versus place payloads differ or what happens with an unknown slug.

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% and both parameters are documented in the schema, so the baseline is 3. The description adds only a mild hint that the identifier can refer to either an event or a place; it says nothing about locale handling or slug format.

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?

The description starts with a specific verb and resource ("Provides the full profile of a specific event or place") and then enumerates exactly what that profile contains, so an agent can distinguish a detail lookup from search or ticket tools. It stops short of naming a sibling (e.g., get_event_tickets) to complete the contrast.

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: the requirement for a specific ID or slug signals this is a follow-up call after a search or listing. There is no explicit statement about when to prefer this over get_event_tickets or get_organizer_profile, and no exclusions.

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.