Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

set_dimmer_level

Set the brightness level of a dimmer switch from 0 (off) to 100 (full brightness) by providing the device index or name.

Instructions

Set the brightness level of a dimmer switch.

Args: level: Integer from 0 to 100. Note: 0 is Off, 100 is Full Brightness. idx: Device index. name: Device name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelYes
idxNo
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the 'set_dimmer_level' tool. It sets the brightness level of a dimmer switch by calling the Domoticz API with 'switchlight' command, 'Set Level' switchcmd, and the level parameter. Validates level (0-100) and resolves device by idx or name.
    async def set_dimmer_level(level: int, idx: int | None = None, name: str | None = None) -> str:
        """Set the brightness level of a dimmer switch.
        
        Args:
            level: Integer from 0 to 100. Note: 0 is Off, 100 is Full Brightness.
            idx: Device index.
            name: Device name.
        """
        if idx is None and name is None:
            return '{"status": "error", "message": "Must provide either idx or name"}'
        if not (0 <= level <= 100):
            return '{"status": "error", "message": "level must be between 0 and 100"}'
        async with create_client() as client:
            resolved_idx = await _resolve_device_idx(client, idx, name)
            if resolved_idx is None:
                return '{"status": "error", "message": "Device not found"}'
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=switchlight&idx={resolved_idx}&switchcmd=Set%20Level&level={level}")
            return response.text
  • Registration of the tool via the @mcp.tool() decorator on the async function, which registers it with the FastMCP instance named 'Domoticz'.
    @mcp.tool()
    async def set_dimmer_level(level: int, idx: int | None = None, name: str | None = None) -> str:
  • Input schema: 'level' (int, 0-100), 'idx' (optional int), 'name' (optional str). The docstring serves as the type/schema definition for the MCP tool.
    async def set_dimmer_level(level: int, idx: int | None = None, name: str | None = None) -> str:
        """Set the brightness level of a dimmer switch.
        
        Args:
            level: Integer from 0 to 100. Note: 0 is Off, 100 is Full Brightness.
            idx: Device index.
            name: Device name.
        """
  • Helper function _resolve_device_idx used by set_dimmer_level to resolve a device by idx or name to its numeric idx.
    async def _resolve_device_idx(client: "httpx.AsyncClient", idx: Optional[int] = None, name: Optional[str] = None) -> Optional[int]:
        """Resolve a device to its idx."""
        return await _resolve_idx(client, idx, name, _device_cache, f"{DOMOTICZ_API_URL}?type=command¶m=getdevices&filter=all&used=true")
  • Helper function _resolve_idx used by _resolve_device_idx to look up entity name->idx using cached API data.
    async def _resolve_idx(
        client: "httpx.AsyncClient",
        idx: Optional[int],
        name: Optional[str],
        cache: Dict[str, Any],
        api_url: str
    ) -> Optional[int]:
        """Resolve an entity to its idx by either using the provided idx or looking up by name."""
        if idx is not None:
            return idx
        if not name:
            return None
        items = await _get_cached_data(client, cache, api_url)
        for item in items:
            if item.get("Name", "").lower() == name.lower():
                return int(str(item.get("idx")))
        return None
Behavior2/5

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

No annotations are provided, and the description only states the basic action without disclosing potential side effects, permissions, or error behavior. The tool performs a write operation (mutates brightness), but no additional behavioral context is given.

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 concise, listing parameters in a clear format. No extraneous information. Front-loaded with the main purpose.

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

Completeness3/5

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

For a simple set operation, the description covers the core action and parameters. However, it lacks context on behavior when both idx and name are provided, conflict resolution, or confirmation of success. Output schema exists but return values are not explained.

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?

Despite 0% schema description coverage, the description adds meaningful details: level's range (0-100) and that 0 is off. It clarifies that idx and name are optional device identifiers. This compensates for the schema's lack of descriptions.

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 clearly states 'Set the brightness level of a dimmer switch,' which specifies verb (set) and resource (dimmer switch). It distinguishes this tool from siblings like set_switch_state (on/off) and control_blinds.

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?

No guidance on when to use this tool versus alternatives (e.g., set_switch_state for non-dimmable switches). No when-not-to-use or prerequisite conditions provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrighem/domoticz-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server