Skip to main content
Glama

events

by xyz.urbanplayground
OverviewDiscussionsAdmin

Create Event Calendar File

create_event_calendar_file
Read-onlyIdempotent

Use this when a user wants to add a Dizko event to their calendar after choosing or buying tickets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / event_id / description
      Removed value: -"Event id returned by search, recommendations, plan_night, get_event, or a ticket quote."
    • removedInput schema / properties / status / description
      Removed value: -"Calendar status, for example CONFIRMED or TENTATIVE."
    • changedOutput 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: +null
  2. Changed3 schema fields changed
    • addedInput schema / properties / event_id / description
      Added value: +"Event id returned by search, recommendations, plan_night, get_event, or a ticket quote."
    • addedInput schema / properties / status / description
      Added value: +"Calendar status, for example CONFIRMED or TENTATIVE."
    • changedOutput 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"
+}
  3. Changed3 schema fields changed
    • removedInput schema / properties / event_id / description
      Removed value: -"Event id returned by search, recommendations, plan_night, get_event, or a ticket quote."
    • removedInput schema / properties / status / description
      Removed value: -"Calendar status, for example CONFIRMED or TENTATIVE."
    • changedOutput 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: +null
  4. First observed

TDQS

B3.1/5.0
Behavior1/5

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

The description says the tool adds an event to a calendar, a write-like side effect, while annotations mark readOnlyHint=true. This is a direct contradiction, and the description provides no other behavioral details such as what file is generated or how the calendar is updated.

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?

One sentence, front-loaded with the 'Use this when' trigger, with no filler. It earns its place despite lacking parameter details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given two parameters, no output schema, and an annotation contradiction, the definition does not tell the agent enough about behavior or return value. It covers the trigger condition but leaves status semantics and the actual calendar-file mechanics unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description fails to explain either parameter. Input schema coverage is 0%, so the agent must rely on the bare names event_id and status, and status remains opaque with no allowed values or purpose. This goes beyond the acceptable baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete use case: add a Dizko event to the user's calendar after ticket choice or purchase. It names both the action and the resource, and no sibling tool covers calendar-file creation, so it is easy to distinguish.

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?

Gives an explicit trigger condition ('after choosing or buying tickets'), which tells an agent when to invoke it. It does not document when not to use it or name alternatives, but the sibling list contains no direct alternative for this task, so the context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All events toolsInspect
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.

Resources