Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_device

Retrieve the current status and details of a specific Domoticz device by 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 accepts optional `idx` or `name` parameters, resolves the device index using `_resolve_device_idx`, makes the API call to Domoticz, and returns the device state as JSON.
    @mcp.tool()
    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 on line 562 registers `get_device` as an MCP tool.
    @mcp.tool()
  • The function signature defines the input schema: `idx` (optional int) and `name` (optional str). The docstring describes the purpose.
    @mcp.tool()
    async def get_device(idx: int | None = None, name: str | None = None) -> str:
  • The `_resolve_device_idx` helper is used by `get_device` to convert a device name to its idx, or pass through an existing idx.
    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 generic `_resolve_idx` helper that performs cached name-to-idx resolution with case-insensitive matching.
    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 are provided, so the description carries the full burden. It indicates a read operation but fails to disclose behavior when both parameters are supplied, device not found, or any side effects. It is adequate but lacks depth.

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 with no wasted words, front-loading the key action and resource.

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?

For a simple getter tool with low parameter count and an output schema, the description covers the essential purpose. However, it misses guidance on parameter combination and error handling, though return values are covered by the output schema.

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%, and the description only mentions 'by IDX or Name' without explaining parameter interaction or precedence. It adds minimal meaning 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 verb 'Get', the resource 'device state', and the identification methods 'by IDX or Name' from Domoticz. It distinguishes from siblings like get_all_devices and search_devices.

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 usage when needing a specific device's state but provides no explicit guidance on when to use versus alternatives, nor any exclusions or prerequisites.

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