Domoticz MCP Server

Overview Schema Source Related Servers Discussions Admin

Update event script

update_event

DestructiveIdempotent

Modify an existing Domoticz event by replacing its name, interpreter, type, and XML source. Requires explicit confirmation to apply high-impact changes.

Instructions

Update script. Cross-ref: domoticz://event/{event_id}. Requires confirm=True.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Event script name
`confirm`	No	Explicitly confirm this high-impact operation
`event_id`	Yes	Canonical Domoticz event ID
`event_type`	Yes	Domoticz event type
`eventstatus`	No	1 to enable the event, 0 to disable it	1
`interpreter`	Yes	Domoticz event interpreter
`xmlstatement`	Yes	Replacement event source or Blockly XML

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
```

Changed24 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"
+}

addedInput schema / properties / event_id / description
```
Added value: +"Canonical Domoticz event ID"
```
addedInput schema / properties / event_id / minimum
```
Added value: +1
```
addedInput schema / properties / event_type / description
```
Added value: +"Domoticz event type"
```
addedInput schema / properties / event_type / maxLength
```
Added value: +50
```
addedInput schema / properties / event_type / minLength
```
Added value: +1
```
addedInput schema / properties / eventstatus / description
```
Added value: +"1 to enable the event, 0 to disable it"
```
addedInput schema / properties / eventstatus / enum
```
Added value: +[
+  "0",
+  "1"
+]
```
addedInput schema / properties / interpreter / description
```
Added value: +"Domoticz event interpreter"
```
addedInput schema / properties / interpreter / maxLength
```
Added value: +50
```
addedInput schema / properties / interpreter / minLength
```
Added value: +1
```
addedInput schema / properties / name / description
```
Added value: +"Event script name"
```
addedInput schema / properties / name / maxLength
```
Added value: +200
```
addedInput schema / properties / name / minLength
```
Added value: +1
```
addedInput schema / properties / xmlstatement / description
```
Added value: +"Replacement event source or Blockly XML"
```
addedInput schema / properties / xmlstatement / maxLength
```
Added value: +1000000
```
addedInput schema / properties / xmlstatement / minLength
```
Added value: +1
```
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: -"update_eventOutput"New value: +"DomoticzToolResult"

First observedv1.1.0May 4, 2026

TDQS

C2.4/5.0

Behavior3/5

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

Annotations already signal destructive and non-read-only behavior, so the description does not need to restate that. It adds a useful behavioral note: `confirm=True` is required despite the schema default of false. However, it does not disclose what is overwritten or any side effects beyond what the destructiveHint annotation already implies.

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

Conciseness3/5

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

The description is very short and front-loaded, but the opening sentence 'Update script' is redundant with the title and does not earn its place. The cross-reference and confirm requirement are useful, but the overall terseness feels like under-specification rather than deliberate conciseness.

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 this is a destructive, idempotent operation with 7 parameters, the description is too thin. It does not explain what the update does to the event, what values are expected for `interpreter`, `event_type`, or `xmlstatement`, nor how this relates to creating events. The output schema reduces the need to document return values, but other context needed for correct invocation is missing.

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 description coverage is 100%, so the schema carries the parameter meanings. The description adds no real parameter semantics except implying that `confirm=True` is mandatory, which is a small addition. The `domoticz://event/{event_id}` cross-reference provides context for `event_id` but not meaningfully beyond the schema.

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

Purpose2/5

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

The description simply says 'Update script,' which largely restates the title 'Update event script' without adding specificity about what kind of script or what updating entails. The cross-reference to `domoticz://event/{event_id}` hints at events, but the purpose is still vague and does not distinguish this from other script-related operations.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives like `create_event`, `update_user_variable`, or `update_device_value`. The instruction 'Requires `confirm=True`' is an invocation requirement, not a usage guideline. No context is given about prerequisites, sequencing, or situations where this tool is the right choice.

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