Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_hardware

Returns all hardware and gateways configured in Domoticz, allowing you to monitor connected smart home devices and their configurations.

Instructions

Get all hardware/gateways configured in Domoticz.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler for the 'get_hardware' tool. It sends a request to the Domoticz API with param=gethardware and returns the raw response text.
    async def get_hardware() -> str:
        """Get all hardware/gateways configured in Domoticz."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=gethardware")
            return response.text
  • Registration of 'get_hardware' as an MCP tool via the @mcp.tool() decorator.
    @mcp.tool()
  • The docstring for the function describes it: 'Get all hardware/gateways configured in Domoticz.'
    async def get_hardware() -> str:
        """Get all hardware/gateways configured in Domoticz."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=gethardware")
            return response.text
  • Test that exercises the get_hardware tool by importing it, mocking the API response, and calling the function.
    from domoticz_mcp.server import get_scenes, switch_scene, get_rooms, get_hardware
    
    # get_scenes
    respx.get(f"{DOMOTICZ_API_URL}?type=command¶m=getscenes").mock(
        return_value=Response(200, json={"result": [{"idx": "1", "Name": "Scene1"}]})
    )
    await get_scenes()
    
    # switch_scene
    respx.get(f"{DOMOTICZ_API_URL}?type=command¶m=switchscene&idx=1&switchcmd=On").mock(
        return_value=Response(200, json={"status": "OK"})
    )
    await switch_scene("On", idx=1)
    
    # get_rooms
    respx.get(f"{DOMOTICZ_API_URL}?type=command¶m=getplans&order=name&used=true").mock(
        return_value=Response(200, json=PLANS_MOCK_RESPONSE)
    )
    await get_rooms()
    
    # get_hardware
    respx.get(f"{DOMOTICZ_API_URL}?type=command¶m=gethardware").mock(
        return_value=Response(200, json={"result": [{"idx": "1", "Name": "Dummy"}]})
    )
    await get_hardware()
  • Mock setup for gethardware API used in test_get_overview, demonstrating the API endpoint used.
    # Mock hardware
    respx.get(f"{DOMOTICZ_API_URL}?type=command¶m=gethardware").mock(
        return_value=Response(200, json={"result": [{"idx": "1"}]})
    )
Behavior2/5

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

No annotations exist, and description provides no insight into performance, data freshness, authentication needs, or side effects. Burden is on description, which falls short.

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?

Single sentence, no wasted words. Front-loaded with action and object.

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?

Tool is simple with no parameters and an output schema. Description adequately conveys purpose; minor gap: could specify what 'hardware' entails (e.g., gateway types).

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?

Zero parameters, so baseline is 4 per guidelines. Description adds no parameter-specific detail, but none is needed given the simple tool.

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 resource 'hardware/gateways', with scope 'all ... configured'. It effectively distinguishes from sibling tools like get_all_devices or get_cameras.

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 versus alternatives (e.g., get_device for specific hardware). Lacks context for exclusivity 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