Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

delete_user_variable

Delete a user variable from Domoticz by providing its IDX or name. Removes the variable from the system.

Instructions

Delete a user variable by IDX or Name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idxNo
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'delete_user_variable' tool handler function. It is decorated with @mcp.tool(), accepts idx or name, resolves the user variable idx using _resolve_user_variable_idx, calls the Domoticz API to delete the user variable, invalidates the cache, and returns the response.
    @mcp.tool()
    async def delete_user_variable(idx: int | None = None, name: str | None = None) -> str:
        """Delete a user variable by IDX or Name."""
        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_user_variable_idx(client, idx, name)
            if resolved_idx is None:
                return '{"status": "error", "message": "User variable not found"}'
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=deleteuservariable&idx={resolved_idx}")
            _user_variable_cache["timestamp"] = 0 # Invalidate cache
            return response.text
  • The '_resolve_user_variable_idx' helper function used by delete_user_variable to resolve a user variable name to its idx by querying the cached user variables.
    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")
  • The generic '_resolve_idx' helper function that resolves an entity to its idx by name, used by _resolve_user_variable_idx.
    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
  • Test for delete_user_variable tool. Shows usage with name='DeleteMe' and the expected mocked HTTP calls.
    # delete_user_variable
    # Mock resolution first
    respx.get(f"{DOMOTICZ_API_URL}?type=command¶m=getuservariables").mock(
        return_value=Response(200, json={"result": [{"idx": "5", "Name": "DeleteMe"}]})
    )
    respx.get(f"{DOMOTICZ_API_URL}?type=command¶m=deleteuservariable&idx=5").mock(
        return_value=Response(200, json={"status": "OK"})
    )
    await delete_user_variable(name="DeleteMe")
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only mentions the delete action. It lacks details on permanence, authorization requirements, error behavior if the variable does not exist, 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.

Conciseness3/5

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

The description is a single short sentence with no redundancy, fitting conciseness. However, it could be slightly expanded to include parameter guidance without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a delete operation) and the presence of sibling tools for add/update, the description lacks completeness. It does not explain return values (though output schema exists), error handling, or how this tool relates to other user variable operations.

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 coverage is 0%, so the description should clarify parameter usage. It states 'by IDX or Name' but does not specify that at least one is required, which one takes precedence if both are provided, or the format of 'name'. The schema's nullable defaults add confusion that the description does not resolve.

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 action ('Delete') and the target resource ('user variable'), and specifies the identification method ('by IDX or Name'). It effectively distinguishes itself from sibling tools like add_user_variable and update_user_variable.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., variable must exist) or typical scenarios. Usage conditions are entirely implied.

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