Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_device

Retrieve the state of a specific smart home device from Domoticz using its IDX or name.

Instructions

Get a specific device state by IDX or Name from Domoticz.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idxNo
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `get_device` tool handler function. It takes an optional idx or name, resolves the device index via `_resolve_device_idx`, and fetches the device state from Domoticz via the `getdevices&rid={idx}` API endpoint. Registered with the `@mcp.tool()` decorator on line 556.
    async def get_device(idx: int | None = None, name: str | None = None) -> str:
        """Get a specific device state by IDX or Name from Domoticz."""
        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=getdevices&rid={resolved_idx}")
            return response.text
  • The `@mcp.tool()` decorator that registers the `get_device` function as an MCP tool.
    @mcp.tool()
  • The `_resolve_device_idx` helper function used by `get_device` (and other device tools). It resolves a device by idx (passthrough) or by 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")
  • The `_simplify_device` helper reduces a device dictionary to essential fields. It is used in resource endpoints but not directly by `get_device` (which returns the raw API response).
    def _simplify_device(dev: Dict[str, Any]) -> Dict[str, Any]:
        """Reduce device dictionary to essential fields to save context space."""
        keys_to_keep = [
            "idx", "Name", "Type", "SubType", "Data", "Status", 
            "BatteryLevel", "Favorite", "HardwareName", "LastUpdate", 
            "TypeImg", "Usage", "CounterToday", "Temp", "Humidity"
        ]
        return {k: dev[k] for k in keys_to_keep if k in dev}
  • The generic `_resolve_idx` helper used by `_resolve_device_idx`. It accepts an optional idx (passthrough) or name (case-insensitive match against cached items).
    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 are provided, and the description does not disclose behaviors like authentication requirements, error states (e.g., what happens if device not found), or side effects. The tool is read-only, but that is not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that conveys the core purpose. It is appropriately concise, though a slight reordering could improve scannability. 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?

Given the presence of an output schema (so return values are documented elsewhere), the description adequately captures the basic function. However, it lacks guidance on parameter usage constraints (e.g., mutual exclusivity, defaults) and error handling, which is needed for a complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description adds only that parameters are identifiers (IDX or Name), but does not explain how they interact (e.g., priority if both given), acceptable formats for 'name', or that one must be provided. This is minimal added value 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 retrieves a specific device state, and specifies the two identification methods (IDX or Name). It effectively distinguishes from sibling tools like 'get_all_devices' and 'get_device_history'.

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?

There is no guidance on when to use this tool versus alternatives (e.g., 'get_all_devices', 'search_devices'). No prerequisites or usage conditions are mentioned, which reduces clarity for an agent deciding between tools.

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