Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

toggle_switch

Toggle a Domoticz switch or light by specifying its IDX or name, with IDX recommended for accuracy.

Instructions

Toggle a switch or light by IDX or Name. Prefer using IDX for precision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idxNo
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the toggle_switch tool. Accepts idx or name, resolves the device index, and sends a 'Toggle' command to the Domoticz API via switchlight endpoint.
    @mcp.tool()
    async def toggle_switch(idx: int | None = None, name: str | None = None) -> str:
        """Toggle a switch or light by IDX or Name. Prefer using IDX for precision."""
        if idx is None and name is None:
            return '{"status": "error", "message": "Must provide either idx or name"}'
        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=Toggle")
            return response.text
  • The tool is registered with the MCP server via the @mcp.tool() decorator on line 574.
    @mcp.tool()
  • Helper function used by toggle_switch to resolve a device idx from a provided idx or name (case-insensitive lookup from cached device list).
    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")
  • Generic helper that resolves an entity (device, scene, variable) to its idx by either direct idx or name-based lookup in a cached list.
    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?

With no annotations provided, the description must disclose behavior. It states the tool toggles a switch/light, but omits details about error handling when no parameters are provided, behavior when both are supplied, or any side effects.

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 a single, concise sentence that immediately conveys the action and options, with no extraneous information.

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?

The description covers the core functionality adequately for a simple toggle, and the presence of an output schema reduces the need to explain return values. It could mention what happens when both parameters are omitted or given simultaneously.

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 compensates by explaining the parameters as 'by IDX or Name' and adds context by recommending IDX for precision, providing meaning beyond the schema's type and default values.

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 states a specific action ('Toggle') on a specific resource ('switch or light') and distinguishes itself by offering two identification methods (IDX or Name) with a preference for IDX, which differentiates it from siblings like 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?

The description provides a clear preference ('Prefer using IDX for precision'), guiding when to use which parameter, but does not explicitly compare with sibling tools like set_switch_state or specify conditions for use.

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