Domoticz MCP Server

by adrighem

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Delete user variable

delete_user_variable

DestructiveIdempotent

Delete a user variable in Domoticz by idx or name. Requires explicit confirmation to prevent accidental removal.

Instructions

Delete var. Preferred: idx. Requires confirm=True.

Input Schema

TableJSON Schema

Name	Required	Description
`idx`	No	Numeric Domoticz idx; preferred over name when known
`name`	No	Case-insensitive Domoticz entity name
`confirm`	No	Explicitly confirm this high-impact operation

Output Schema

TableJSON Schema

Name	Required	Description	Default
`title`	No	Optional Domoticz response title
`status`	Yes	Status returned by Domoticz, normally OK

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.4.0Sep 14, 2026
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

Changed12 schema fields changedv1.3.1Jul 26, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Explicitly confirm this high-impact operation",
+  "title": "Confirm",
+  "type": "boolean"
+}

changedInput schema / properties / idx / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / idx / description

Added value: +"Numeric Domoticz idx; preferred over name when known"

changedInput schema / properties / name / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / name / description

Added value: +"Case-insensitive Domoticz entity name"

addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / description

Added value: +"A successful Domoticz command response."

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / status

Added value: +{
+  "description": "Status returned by Domoticz, normally OK",
+  "title": "Status",
+  "type": "string"
+}

addedOutput schema / properties / title

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional Domoticz response title",
+  "title": "Title"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "status"
+]

changedOutput schema / title

Previous value: -"delete_user_variableOutput"New value: +"DomoticzToolResult"

First observedv1.1.0May 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the critical requirement 'Requires confirm=True', which is a behavioral condition not fully captured by annotations. This is valuable context for the agent to know the operation will not proceed without explicit confirmation, beyond what the schema or annotations alone provide.

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 two short sentences with zero filler. It front-loads the purpose, then adds the key usage notes. Every word earns its place, and it is immediately scannable.

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 simple deletion operation, the description covers the necessary points: what it does, the preferred identifier, and the confirmation requirement. Annotations cover the destructive nature, and the schema details each parameter. The presence of an output schema means return values need not be explained. It misses edge cases like what happens if both idx and name are provided, but these are minor and likely handled by the system or output schema.

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

Parameters4/5

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

Schema coverage is 100%, so each parameter is already described in the schema. The description adds the explicit requirement that confirm must be true, which is not stated as a requirement in the schema (only as 'Explicitly confirm this high-impact operation'). It also reinforces that idx is preferred over name, matching the schema's note but adding a clear directive. This elevates the description above the schema baseline.

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 title clearly states 'Delete user variable', and the description 'Delete var' is a concise shorthand that identifies the verb and resource. The addition of 'Preferred: idx' distinguishes it from name-based deletion, though it doesn't explicitly differentiate from other delete tools. Clear enough for an agent to understand the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by stating 'Preferred: idx' and 'Requires confirm=True', which give conditional guidance. However, it does not explicitly state when to use this tool over alternatives like delete_device or update_user_variable, nor does it mention scenarios where deletion should be avoided. The guidance is implied rather than explicit.

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