Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

switch_scene

Turn a scene or group on, off, or toggle it using its IDX or name in Domoticz. Scenes support only On command.

Instructions

Turn a scene or group On or Off by IDX or Name in Domoticz. command must be 'On', 'Off', or 'Toggle'. Scenes can only be turned 'On'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes
idxNo
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'switch_scene' MCP tool. Validates that idx or name is provided, validates command is 'On', 'Off', or 'Toggle', resolves the scene idx (by idx or by name), and calls the Domoticz API with param=switchscene.
    async def switch_scene(command: str, idx: int | None = None, name: str | None = None) -> str:
        """Turn a scene or group On or Off by IDX or Name in Domoticz. command must be 'On', 'Off', or 'Toggle'. Scenes can only be turned 'On'."""
        if idx is None and name is None:
            return '{"status": "error", "message": "Must provide either idx or name"}'
        if command.capitalize() not in ['On', 'Off', 'Toggle']:
            return '{"status": "error", "message": "command must be \'On\', \'Off\', or \'Toggle\'"}'
        async with create_client() as client:
            resolved_idx = await _resolve_scene_idx(client, idx, name)
            if resolved_idx is None:
                return '{"status": "error", "message": "Scene not found"}'
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=switchscene&idx={resolved_idx}&switchcmd={command.capitalize()}")
            return response.text
  • The @mcp.tool() decorator registers the switch_scene function as an MCP tool on line 671.
    @mcp.tool()
  • Docstring/type hints define the schema: 'command' (str: On/Off/Toggle), 'idx' (optional int), 'name' (optional str).
    """Turn a scene or group On or Off by IDX or Name in Domoticz. command must be 'On', 'Off', or 'Toggle'. Scenes can only be turned 'On'."""
  • Helper function _resolve_scene_idx used by switch_scene to resolve a scene idx from either a direct idx or a name lookup, using _resolve_idx with the scene cache.
    async def _resolve_scene_idx(client: "httpx.AsyncClient", idx: Optional[int] = None, name: Optional[str] = None) -> Optional[int]:
        """Resolve a scene to its idx."""
        return await _resolve_idx(client, idx, name, _scene_cache, f"{DOMOTICZ_API_URL}?type=command¶m=getscenes")
  • Generic _resolve_idx helper that either passes through a provided idx or looks up an entity by name in 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
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses allowed commands and a scene-specific constraint, but does not detail error behavior, permissions, rate limits, or side effects like what happens when toggling a scene.

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 three short sentences, each adding distinct value: purpose, command options, and a critical constraint. No unnecessary words.

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?

Covers essential usage for a simple tool but omits details like error handling, behavior when both idx and name are given, or output format. The presence of an output schema partially compensates, but more context would improve completeness.

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 0%, so the description must add meaning. It specifies allowed values for 'command' and indicates that 'idx' and 'name' identify the target, but does not explain their interaction or priority when both are provided.

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 the action ('Turn On or Off'), resource ('scene or group'), and method ('by IDX or Name'), distinguishing it from sibling tools like toggle_switch or set_switch_state.

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?

Provides clear context for when to use the tool (to control scenes/groups) and includes a specific constraint ('Scenes can only be turned On'). However, it lacks explicit guidance on when not to use it or how it compares to alternatives.

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