create_event_calendar_fileUse this when a user wants to add a Dizko event to their calendar after choosing or buying tickets.
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | ||
| event_id | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / event_id / descriptionRemoved value: -"Event id returned by search, recommendations, plan_night, get_event, or a ticket quote."Input schema / properties / status / descriptionRemoved value: -"Calendar status, for example CONFIRMED or TENTATIVE."Output schema / (root)Previous value: -{
- "anyOf": [
- {
- "properties": {
- "assistant_instruction": {
- "type": "string"
- },
- "calendar_event": {
- "properties": {
- "city": {
- "type": [
- "string",
- "null"
- ]
- },
- "ends_at": {
- "type": [
- "string",
- "null"
- ]
- },
- "event_url": {
- "type": [
- "string",
- "null"
- ]
- },
- "ics_content": {
- "type": "string"
- },
- "ics_filename": {
- "type": "string"
- },
- "starts_at": {
- "type": [
- "string",
- "null"
- ]
- },
- "status": {
- "type": "string"
- },
- "ticket_url": {
- "type": [
- "string",
- "null"
- ]
- },
- "title": {
- "type": [
- "string",
- "null"
- ]
- },
- "uid": {
- "type": "string"
- },
- "venue": {
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "uid",
- "ics_filename",
- "ics_content"
- ],
- "type": [
- "object",
- "null"
- ]
- }
- },
- "required": [
- "calendar_event"
- ],
- "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: +nullInput schema / properties / event_id / descriptionAdded value: +"Event id returned by search, recommendations, plan_night, get_event, or a ticket quote."Input schema / properties / status / descriptionAdded value: +"Calendar status, for example CONFIRMED or TENTATIVE."Output schema / (root)Previous value: -nullNew value: +{
+ "anyOf": [
+ {
+ "properties": {
+ "assistant_instruction": {
+ "type": "string"
+ },
+ "calendar_event": {
+ "properties": {
+ "city": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "ends_at": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "event_url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "ics_content": {
+ "type": "string"
+ },
+ "ics_filename": {
+ "type": "string"
+ },
+ "starts_at": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "type": "string"
+ },
+ "ticket_url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "title": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "uid": {
+ "type": "string"
+ },
+ "venue": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "uid",
+ "ics_filename",
+ "ics_content"
+ ],
+ "type": [
+ "object",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "calendar_event"
+ ],
+ "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"
+}Input schema / properties / event_id / descriptionRemoved value: -"Event id returned by search, recommendations, plan_night, get_event, or a ticket quote."Input schema / properties / status / descriptionRemoved value: -"Calendar status, for example CONFIRMED or TENTATIVE."Output schema / (root)Previous value: -{
- "anyOf": [
- {
- "properties": {
- "assistant_instruction": {
- "type": "string"
- },
- "calendar_event": {
- "properties": {
- "city": {
- "type": [
- "string",
- "null"
- ]
- },
- "ends_at": {
- "type": [
- "string",
- "null"
- ]
- },
- "event_url": {
- "type": [
- "string",
- "null"
- ]
- },
- "ics_content": {
- "type": "string"
- },
- "ics_filename": {
- "type": "string"
- },
- "starts_at": {
- "type": [
- "string",
- "null"
- ]
- },
- "status": {
- "type": "string"
- },
- "ticket_url": {
- "type": [
- "string",
- "null"
- ]
- },
- "title": {
- "type": [
- "string",
- "null"
- ]
- },
- "uid": {
- "type": "string"
- },
- "venue": {
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "uid",
- "ics_filename",
- "ics_content"
- ],
- "type": [
- "object",
- "null"
- ]
- }
- },
- "required": [
- "calendar_event"
- ],
- "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: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says the tool 'add[s]' an event to a calendar, implying a state-changing write operation, while annotations declare readOnlyHint=true. This is a direct contradiction. No additional behavioral context is provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, front-loaded with the intended use case and devoid of filler. It is structurally clean, though its brevity comes at the cost of behavioral and parameter detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and two undocumented parameters, the description gives only selection context. It omits what the resulting calendar file contains, how 'status' affects behavior, and the contradiction with readOnlyHint is unresolved.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 for undocumented parameters. It only mentions adding an event and does not explain 'event_id' or, more importantly, 'status', leaving the agent without the information needed to set parameters correctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific use case: adding a Dizko event to the user's calendar after ticket selection/purchase. It identifies the action and resource, though it does not explicitly differentiate itself from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a clear trigger: use when the user wants to add an event after choosing or buying tickets. It does not mention when not to use it or name alternative tools, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.