Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_user_variables

Retrieve all user variables from Domoticz to monitor and manage custom data in your home automation system.

Instructions

Get all user variables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_user_variables' tool. It is decorated with @mcp.tool() and registers itself as an MCP tool named 'get_user_variables'. It fetches all user variables from Domoticz via the cached API call and returns them as JSON.
    @mcp.tool()
    async def get_user_variables() -> str:
        """Get all user variables."""
        async with create_client() as client:
            vars = await _get_cached_data(client, _user_variable_cache, f"{DOMOTICZ_API_URL}?type=command¶m=getuservariables")
            return json.dumps({"status": "OK", "result": vars})
  • Cache object for user variables, used by the get_user_variables handler to cache results with a TTL of 5 minutes.
    _user_variable_cache = {"data": None, "timestamp": 0}
  • Generic caching helper (_get_cached_data) that the handler uses to fetch and cache user variable data from the Domoticz API.
    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"]
  • Helper to resolve a user variable's idx by its name, used by other user variable tools (add, update, delete).
    async def _resolve_user_variable_idx(client: "httpx.AsyncClient", idx: Optional[int] = None, name: Optional[str] = None) -> Optional[int]:
        """Resolve a user variable to its idx."""
        return await _resolve_idx(client, idx, name, _user_variable_cache, f"{DOMOTICZ_API_URL}?type=command¶m=getuservariables")
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits such as side effects, performance implications, or authentication requirements. For a read operation, minimal disclosure but no extra context beyond the bare fact.

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?

Extremely concise: a single phrase that clearly states purpose. No wasted words.

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 zero parameters and presence of an output schema, the description is nearly complete. It lacks mention of what the output contains or any scope (e.g., current user), but these are implied by the tool's name and siblings.

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?

The tool has no parameters and schema coverage is 100%. The description adds no extra semantics but is not required to since there are no parameters. Baseline 4 is appropriate.

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 'Get all user variables' clearly states the action (get) and resource (user variables), distinguishing it from sibling tools that add, delete, or update user variables.

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 like add_user_variable or search_scripts. No context about filtering or prerequisites provided.

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