events

Delete Event Preferences

delete_event_preferences

Destructive

Use this only when a user asks to delete their Dizko saved event preferences and feedback history.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`profile_id`	Yes
`confirm_delete`	Yes
`profile_secret`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedAug 30, 2026

removedInput schema / properties / confirm_delete / description

Removed value: -"Must be true only after the user confirms deletion of Dizko connector preferences and feedback history."

removedInput schema / properties / profile_id / description
```
Removed value: -"Stable user/profile id."
```

removedInput schema / properties / profile_secret / description

Removed value: -"Private profile secret returned when the profile was created."

changedOutput schema / (root)

Previous value: -{
-  "anyOf": [
-    {
-      "properties": {
-        "deleted": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "deleted"
-      ],
-      "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

Changed4 schema fields changedAug 24, 2026

addedInput schema / properties / confirm_delete / description

Added value: +"Must be true only after the user confirms deletion of Dizko connector preferences and feedback history."

addedInput schema / properties / profile_id / description
```
Added value: +"Stable user/profile id."
```

addedInput schema / properties / profile_secret / description

Added value: +"Private profile secret returned when the profile was created."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "deleted": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "deleted"
+      ],
+      "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"
+}

Changed4 schema fields changedAug 24, 2026

removedInput schema / properties / confirm_delete / description

Removed value: -"Must be true only after the user confirms deletion of Dizko connector preferences and feedback history."

removedInput schema / properties / profile_id / description
```
Removed value: -"Stable user/profile id."
```

removedInput schema / properties / profile_secret / description

Removed value: -"Private profile secret returned when the profile was created."

changedOutput schema / (root)

Previous value: -{
-  "anyOf": [
-    {
-      "properties": {
-        "deleted": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "deleted"
-      ],
-      "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 observedJul 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The destructiveHint annotation already flags mutation, and the description adds useful scope by disclosing that both preferences and feedback history are deleted. It also adds a consent precondition ('only when a user asks'), which is relevant behavioral context beyond the annotation.

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 a single front-loaded sentence with no wasted words. It efficiently communicates both purpose and usage trigger.

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

Completeness1/5

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

For a destructive tool with three required parameters, no output schema, and zero schema coverage, this description is far too thin. An agent cannot infer the role of profile_secret, the semantics of confirm_delete, or the nature of the deletion (permanence, cascading effects), making it inadequate for safe invocation.

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?

Schema description coverage is 0%, so the description must compensate by explaining the three required parameters, but it does not. Nothing clarifies what profile_id, profile_secret, or confirm_delete mean, how they relate to each other, or that confirm_delete likely gates the destructive action.

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?

The description names a specific verb ('delete') and a precise resource ('Dizko saved event preferences and feedback history'), which clearly distinguishes it from sibling tools like get_event_preferences or save_event_preferences. The phrase 'only when a user asks' further pins down the intended action.

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 explicitly states when to use the tool: only when the user asks to delete their saved event preferences and feedback history. The word 'only' provides an implicit when-not, but the description does not name alternative tools for related intents such as saving or retrieving preferences.

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

All events tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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.

Resources

Need Help?