Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

switch_scene

Turn a Domoticz scene or group On, Off, or Toggle using its IDX or name. 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 main handler function for the 'switch_scene' tool. Decorated with @mcp.tool(), it accepts a command ('On', 'Off', 'Toggle'), an optional idx, and an optional name. It resolves the scene idx (via name if needed), then calls the Domoticz API with 'switchscene' parameter.
    @mcp.tool()
    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 tool is registered via the @mcp.tool() decorator on the switch_scene async function at line 665.
    @mcp.tool()
  • The schema/type definition for switch_scene parameters: command (str), idx (int | None), name (str | None). The docstring defines the command as 'On', 'Off', or 'Toggle'.
    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'."""
  • Helper function _resolve_scene_idx used by switch_scene to resolve a scene's idx from either a direct idx or a name lookup via 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 helper _resolve_idx that resolves an entity's idx by either direct idx or name lookup from 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 exist, so the description carries the full burden. It provides key behavioral info (command values, scenes only On), but lacks details on consequences, error handling, authentication needs, or whether the action is reversible. The description is partially transparent but incomplete.

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 sentences, front-loaded with the primary action, and every sentence adds value. No redundant or extraneous content.

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?

Given parameter count (3) and lack of annotations, the description covers purpose, command constraints, and a behavioral limitation. However, it does not clarify whether idx or name is required (schema says both nullable), nor describe the output schema or error scenarios. It is functional but has notable gaps.

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 0%, so the description must compensate. It adds critical semantics: command must be 'On', 'Off', or 'Toggle' (not in schema enums), and identification is by IDX or Name. This clarifies parameter usage beyond the schema's type-only definitions.

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 tool turns a scene or group On or Off by IDX or Name in Domoticz, specifying the action and target. It distinguishes from sibling tools (e.g., toggle_switch, set_switch_state) by focusing on scenes/groups and noting that scenes can only be turned On.

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?

The description implies usage for scenes and groups, and lists valid commands ('On', 'Off', 'Toggle') with the note that scenes only accept 'On'. However, it does not explicitly contrast with alternatives like toggle_switch or set_switch_state, nor provide when-not-to-use guidance.

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