Get Event
get_eventRead-only
Use this when a user asks for details about a Dizko event id.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
events
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Changed2 schema fields changed
- removed
Input schema / properties / id / descriptionRemoved value: -"Event id." - changed
Output schema / (root)Previous value: -{ - "anyOf": [ - { - "properties": { - "app_download_url": { - "description": "Dizko iPhone app landing page.", - "type": "string" - }, - "assistant_instruction": { - "type": "string" - }, - "attendance_count": { - "type": [ - "number", - "null" - ] - }, - "calendar_url": { - "description": "Prefilled Google Calendar link. Offer as 'Add to calendar'.", - "type": [ - "string", - "null" - ] - }, - "city": { - "type": [ - "string", - "null" - ] - }, - "description": { - "description": "Short one-line event description for display.", - "type": [ - "string", - "null" - ] - }, - "directions_url": { - "description": "Google Maps directions link. Offer as 'Get directions'.", - "type": [ - "string", - "null" - ] - }, - "ends_at": { - "type": [ - "string", - "null" - ] - }, - "event_types": { - "items": { - "type": "string" - }, - "type": "array" - }, - "event_url": { - "type": "string" - }, - "genres": { - "items": { - "type": "string" - }, - "type": "array" - }, - "id": { - "type": "string" - }, - "lineup": { - "items": { - "type": "string" - }, - "type": "array" - }, - "price": { - "type": [ - "string", - "null" - ] - }, - "source": { - "type": [ - "string", - "null" - ] - }, - "starts_at": { - "type": [ - "string", - "null" - ] - }, - "ticket_url": { - "type": [ - "string", - "null" - ] - }, - "title": { - "type": "string" - }, - "venue": { - "type": [ - "string", - "null" - ] - }, - "vibe": { - "items": { - "type": "string" - }, - "type": "array" - } - }, - "required": [ - "id", - "title", - "event_url" - ], - "type": "object" - }, - { - "properties": { - "assistant_instruction": { - "type": "string" - }, - "cause": { - "type": [ - "string", - "null" - ] - }, - "classification": { - "type": [ - "string", - "null" - ] - }, - "code": { - "type": [ - "string", - "null" - ] - }, - "error": { - "type": "string" - }, - "hostname": { - "type": [ - "string", - "null" - ] - }, - "retryable": { - "type": "boolean" - }, - "status": { - "type": [ - "number", - "null" - ] - }, - "type": { - "type": "string" - }, - "url": { - "type": [ - "string", - "null" - ] - } - }, - "required": [ - "error" - ], - "type": "object" - } - ], - "type": "object" -}New value: +null
Changed2 schema fields changed
- added
Input schema / properties / id / descriptionAdded value: +"Event id." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "anyOf": [ + { + "properties": { + "app_download_url": { + "description": "Dizko iPhone app landing page.", + "type": "string" + }, + "assistant_instruction": { + "type": "string" + }, + "attendance_count": { + "type": [ + "number", + "null" + ] + }, + "calendar_url": { + "description": "Prefilled Google Calendar link. Offer as 'Add to calendar'.", + "type": [ + "string", + "null" + ] + }, + "city": { + "type": [ + "string", + "null" + ] + }, + "description": { + "description": "Short one-line event description for display.", + "type": [ + "string", + "null" + ] + }, + "directions_url": { + "description": "Google Maps directions link. Offer as 'Get directions'.", + "type": [ + "string", + "null" + ] + }, + "ends_at": { + "type": [ + "string", + "null" + ] + }, + "event_types": { + "items": { + "type": "string" + }, + "type": "array" + }, + "event_url": { + "type": "string" + }, + "genres": { + "items": { + "type": "string" + }, + "type": "array" + }, + "id": { + "type": "string" + }, + "lineup": { + "items": { + "type": "string" + }, + "type": "array" + }, + "price": { + "type": [ + "string", + "null" + ] + }, + "source": { + "type": [ + "string", + "null" + ] + }, + "starts_at": { + "type": [ + "string", + "null" + ] + }, + "ticket_url": { + "type": [ + "string", + "null" + ] + }, + "title": { + "type": "string" + }, + "venue": { + "type": [ + "string", + "null" + ] + }, + "vibe": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "id", + "title", + "event_url" + ], + "type": "object" + }, + { + "properties": { + "assistant_instruction": { + "type": "string" + }, + "cause": { + "type": [ + "string", + "null" + ] + }, + "classification": { + "type": [ + "string", + "null" + ] + }, + "code": { + "type": [ + "string", + "null" + ] + }, + "error": { + "type": "string" + }, + "hostname": { + "type": [ + "string", + "null" + ] + }, + "retryable": { + "type": "boolean" + }, + "status": { + "type": [ + "number", + "null" + ] + }, + "type": { + "type": "string" + }, + "url": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "error" + ], + "type": "object" + } + ], + "type": "object" +}
Changed2 schema fields changed
- removed
Input schema / properties / id / descriptionRemoved value: -"Event id." - changed
Output schema / (root)Previous value: -{ - "anyOf": [ - { - "properties": { - "app_download_url": { - "description": "Dizko iPhone app landing page.", - "type": "string" - }, - "assistant_instruction": { - "type": "string" - }, - "attendance_count": { - "type": [ - "number", - "null" - ] - }, - "calendar_url": { - "description": "Prefilled Google Calendar link. Offer as 'Add to calendar'.", - "type": [ - "string", - "null" - ] - }, - "city": { - "type": [ - "string", - "null" - ] - }, - "description": { - "description": "Short one-line event description for display.", - "type": [ - "string", - "null" - ] - }, - "directions_url": { - "description": "Google Maps directions link. Offer as 'Get directions'.", - "type": [ - "string", - "null" - ] - }, - "ends_at": { - "type": [ - "string", - "null" - ] - }, - "event_types": { - "items": { - "type": "string" - }, - "type": "array" - }, - "event_url": { - "type": "string" - }, - "genres": { - "items": { - "type": "string" - }, - "type": "array" - }, - "id": { - "type": "string" - }, - "lineup": { - "items": { - "type": "string" - }, - "type": "array" - }, - "price": { - "type": [ - "string", - "null" - ] - }, - "source": { - "type": [ - "string", - "null" - ] - }, - "starts_at": { - "type": [ - "string", - "null" - ] - }, - "ticket_url": { - "type": [ - "string", - "null" - ] - }, - "title": { - "type": "string" - }, - "venue": { - "type": [ - "string", - "null" - ] - }, - "vibe": { - "items": { - "type": "string" - }, - "type": "array" - } - }, - "required": [ - "id", - "title", - "event_url" - ], - "type": "object" - }, - { - "properties": { - "assistant_instruction": { - "type": "string" - }, - "cause": { - "type": [ - "string", - "null" - ] - }, - "classification": { - "type": [ - "string", - "null" - ] - }, - "code": { - "type": [ - "string", - "null" - ] - }, - "error": { - "type": "string" - }, - "hostname": { - "type": [ - "string", - "null" - ] - }, - "retryable": { - "type": "boolean" - }, - "status": { - "type": [ - "number", - "null" - ] - }, - "type": { - "type": "string" - }, - "url": { - "type": [ - "string", - "null" - ] - } - }, - "required": [ - "error" - ], - "type": "object" - } - ], - "type": "object" -}New value: +null
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the tool's safe read behavior is known without the description. The description adds no extra behavioral context such as error handling, response format, or what happens for missing IDs, but for a read-only getter this is acceptable.
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?
The description is one short, direct sentence with no filler. It delivers the usage condition and parameter meaning efficiently.
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?
Given the tool's simplicity—one required parameter, read-only annotation, no output schema—the description covers the essential purpose and parameter. Some ambiguity remains about the return shape and behavior for invalid IDs, but this is minor for a straightforward getter.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, but the description compensates by identifying the single parameter 'id' as a 'Dizko event id.' This gives the agent enough semantic understanding to select the right value, though it does not specify format or source.
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 states a specific verb ('details about') and resource ('Dizko event id'), which clearly indicates this is a by-ID lookup. It is distinct enough from siblings like get_artist_events or search_events, though it does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use this when a user asks for details about a Dizko event id,' providing a clear trigger condition. It does not state exclusions or alternative tools, but the usage context is unambiguous for a simple lookup.
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.
TDQS
B3.2/5.0
Disambiguation4/5
Most tools map to distinct actions across search, recommendations, preferences, tickets, and feedback, with clear descriptions. The only real ambiguity is between recommend_events and recommend_events_for_user, plus some follow-up overlap, but boundaries are mostly clear.
Naming Consistency4/5
Tool names follow a consistent imperative verb_noun pattern and use snake_case throughout. Minor inconsistency exists in event vs events pluralization and interchangeable create/save verbs, but the overall pattern is predictable.
Tool Count3/5
23 tools is a large surface for an events assistant, landing in the 16-25 range that feels heavy. The count is defensible given the breadth of features, but it is borderline and somewhat difficult to navigate.
Completeness4/5
The set covers the core consumer journey well: search, recommendations, preference onboarding and CRUD, ticket quoting and purchase, and post-event feedback. Missing order-status or refund/cancellation endpoints are minor gaps, but primary workflows do not hit dead ends.