Get Event
get_eventRead-onlyIdempotent
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.
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.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already provide a strong safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true), so the description does not need to restate that. However, the description adds no extra behavioral context beyond 'details', such as what happens for a missing event or what the response contains.
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 concise sentence, front-loaded with a clear usage trigger and no wasted words. It is easy to parse and directly actionable.
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?
For a one-parameter read-only tool with rich annotations and no output schema, the description provides the core trigger and scope. It does not elaborate on return values or error cases, but 'details' plus the annotations make the tool adequately callable.
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 0%, so the description must compensate. It does identify the lone 'id' parameter as a Dizko event id, adding domain meaning beyond the bare schema. It does not offer format or examples, but that is a minor gap for a single string parameter.
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 clear action ('get details') and a specific resource ('a Dizko event id'), making the tool's purpose easy to grasp. It does not explicitly differentiate itself from sibling search/get tools, but the phrase 'event id' signals a by-ID lookup.
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?
It gives a clear use condition: when the user asks for details about a specific event ID. It does not mention when not to use it or name alternatives like search_events, but the contextual trigger is sufficient for a simple lookup tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.