Domoticz MCP Server

Overview Schema Source Related Servers Discussions Admin

Set dimmer level

set_dimmer_level

DestructiveIdempotent

Adjust a dimmer device's brightness to a specified percentage (0-100) using its Domoticz ID or name, enabling precise lighting control.

Instructions

Set brightness (0-100). Preferred: idx. Cross-ref: domoticz://device/{idx}.

Input Schema

TableJSON Schema

Name	Required	Description
`idx`	No	Numeric Domoticz idx; preferred over name when known
`name`	No	Case-insensitive Domoticz entity name
`level`	Yes	Brightness percentage

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

Changed14 schema fields changedv1.3.1Jul 26, 2026

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"

addedInput schema / properties / level / description
```
Added value: +"Brightness percentage"
```
addedInput schema / properties / level / maximum
```
Added value: +100
```
addedInput schema / properties / level / minimum
```
Added value: +0
```

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: -"set_dimmer_levelOutput"New value: +"DomoticzToolResult"

First observedv1.1.0May 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the behavioral state-changing nature is covered. The description adds no extra behavioral context such as side effects, device state impacts, or error behavior. It does not contradict the annotations, so a mid-range score is appropriate.

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?

The description is short, with each sentence serving a purpose: stating the action, noting the preferred parameter, and providing a cross-reference. It is front-loaded with the core function. It earns a high score for conciseness, though the cross-reference could be seen as slightly tangential.

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 setter tool, the description covers the essential action, value range, and preferred identifier. The output schema and full parameter descriptions fill most remaining gaps. A minor omission is clarifying that idx or name must be supplied, though this is inferable from the schema and the 'preferred' note.

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 baseline is 3. The description's 'Preferred: idx' reinforces the schema's own note that idx is preferred over name, adding no new semantic content. The description does not explain the name parameter or clarify that at least one identifier is needed, but the schema already covers these details.

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 description states a specific action ('Set brightness') and resource ('dimmer level') with a range (0-100), making the tool's purpose immediately clear. It does not explicitly differentiate from siblings like set_color_brightness, but the tool name and the brightness range help disambiguate. This is clear but lacks explicit sibling differentiation.

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?

The description offers no guidance on when to choose this tool over alternatives such as set_switch_state or set_color_brightness. The only usage hint is 'Preferred: idx', which concerns parameter selection rather than tool selection. There are no exclusions or alternative references.

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