Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_scene_devices

Retrieve all devices assigned to a specific scene or group by providing its IDX or name for home automation management.

Instructions

List all devices belonging to a specific scene/group by IDX or Name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idxNo
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler function for 'get_scene_devices'. It resolves a scene by idx or name, then fetches all devices belonging to that scene via the Domoticz API endpoint 'getscenedevices'.
    @mcp.tool()
    async def get_scene_devices(idx: int | None = None, name: str | None = None) -> str:
        """List all devices belonging to a specific scene/group by IDX or Name."""
        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_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=getscenedevices&idx={resolved_idx}&isscene=true")
            return response.text
  • The tool is registered with the MCP server via the @mcp.tool() decorator on line 1061.
    @mcp.tool()
  • Helper used by get_scene_devices to resolve a scene's idx by name or direct idx, using the _resolve_idx shared utility 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")
  • Shared helper used by _resolve_scene_idx to lookup items by name in cached 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 provided. The description only states it lists devices, implying read-only, but does not disclose return format, pagination, error handling, or behavior for missing/conflicting parameters. Deeper behavioral context is absent.

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?

One concise sentence of 12 words, front-loading the purpose with no redundancy. Every word earns its place.

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?

The description does not mention the output schema (though one exists), nor does it clarify whether at least one parameter is required. For a simple tool with two optional params, more completeness around usage would be helpful.

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 coverage is 0%, and the description adds the nuance that IDX or Name are alternative identifiers. However, it does not clarify precedence if both are provided, nor does it describe valid formats or constraints beyond the schema.

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 lists devices for a specific scene/group, specifying identification by IDX or Name. This distinguishes it from siblings like get_scenes (lists scenes) and get_all_devices.

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 vs alternatives (e.g., search_devices), no prerequisites mentioned, and no indication of required parameters or behavior when both IDX and Name are omitted.

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