events

Delete Event Preferences

delete_event_preferences

DestructiveIdempotent

Use this only when the user confirms they want their Dizko connector data deleted. Deletes a profile's saved preferences and feedback history; confirm_delete must be true. Scoped to Dizko only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile_id": "<profile_id>",
      "profile_secret": "<profile_secret>",
      "confirm_delete": "<confirm_delete>"
    },
    "name": "delete_event_preferences"
  }
}

Input Schema

Name	Required	Description
`profile_id`	Yes
`confirm_delete`	Yes	Must be true only after the user confirms deletion.
`profile_secret`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026
- addedInput schema / properties / confirm_delete / description
```
Added value: +"Must be true only after the user confirms deletion."
```
- addedInput schema / properties / profile_id / maxLength
```
Added value: +200
```
- addedInput schema / properties / profile_secret / maxLength
```
Added value: +200
```

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

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds the confirmation requirement, the exact data destroyed (preferences and feedback history), and the Dizko-only scope. It stops short of stating irreversibility or what happens to the profile record itself, so it is good but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the precondition and the confirmation requirement front-loaded, followed by scope. No filler, though the imperative and the 'must be true' clause overlap slightly with the schema's own text.

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 destructive, non-idempotent-looking mutation with no output schema, the description covers the essentials an agent needs before calling: user confirmation, what gets removed, and scope. The main remaining gaps are the semantics of profile_secret and whether the deletion is reversible.

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 coverage is only 33% (confirm_delete is the sole documented parameter), so the description carries extra burden. It does reinforce the confirm_delete=true gate, but profile_id and profile_secret are left without any description-level meaning, so it only partly compensates for the gap.

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?

Uses a specific verb (deletes) plus the exact resource (a profile's saved preferences and feedback history), which clearly separates it from the sibling read/write pair get_event_preferences and save_event_preferences. The scope qualifier ('Scoped to Dizko only') further pins down what this tool touches.

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 an explicit gating condition: use it only when the user confirms they want their Dizko data deleted. That is real when-to-use guidance, though it never names the alternative tools (e.g., save_event_preferences for modification) that an agent might confuse it with.

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

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

Need Help?