Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_scenes

Retrieve all scenes and groups configured in your Domoticz home automation system.

Instructions

Get all scenes and groups from Domoticz.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_scenes' tool. Uses the DomoticzClient to call the Domoticz API with param=getscenes, caches the result via _get_cached_data, and returns the scenes as JSON.
    @mcp.tool()
    async def get_scenes() -> str:
        """Get all scenes and groups from Domoticz."""
        async with create_client() as client:
            scenes = await _get_cached_data(client, _scene_cache, f"{DOMOTICZ_API_URL}?type=command¶m=getscenes")
            return json.dumps({"status": "OK", "result": scenes})
  • Registration: The @mcp.tool() decorator registers 'get_scenes' as a tool in the FastMCP server instance.
    @mcp.tool()
    async def get_scenes() -> str:
        """Get all scenes and groups from Domoticz."""
  • Helper function used by get_scenes to fetch and cache data from the Domoticz API, with a 5-minute TTL.
    async def _get_cached_data(client: "httpx.AsyncClient", cache_obj: Dict[str, Any], api_url: str, key_path: str = "result") -> List[Dict[str, Any]]:
        now = time.time()
        if cache_obj["data"] is None or (now - cache_obj["timestamp"]) > CACHE_TTL:
            response = await _do_request(client, "GET", api_url)
            cache_obj["data"] = response.json().get(key_path, [])
            cache_obj["timestamp"] = now
        return cache_obj["data"]
  • Global cache object for scenes, used by get_scenes to avoid repeated API calls.
    _scene_cache = {"data": None, "timestamp": 0}
    _user_variable_cache = {"data": None, "timestamp": 0}
    _plans_cache = {"data": None, "timestamp": 0}
  • Helper to resolve a scene by name or idx, used by other scene-related tools (e.g., switch_scene, get_scene_devices). Uses the same _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")
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states what the tool does (get scenes/groups) but does not mention read-only nature, authentication, rate limits, 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 sentence with no redundancy. Every word is necessary, achieving maximum conciseness.

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?

Given no parameters and an existing output schema, the description is nearly complete. It could mention the output includes scene and group names/IDs, but the schema likely covers that.

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?

There are no parameters, and schema coverage is 100% (trivially). The description adds no parameter info, but with zero parameters, the baseline is 4. No additional meaning is needed.

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 verb 'Get' and the resource 'all scenes and groups from Domoticz', which is specific and distinct from siblings like 'get_scene_devices' and 'switch_scene'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the purpose but offers no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It is minimal but not misleading.

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