Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_settings

Retrieve global Domoticz settings and configuration to access system-wide parameters for home automation control.

Instructions

Get global Domoticz settings and configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `get_settings` tool handler function. It is registered as an MCP tool via @mcp.tool() decorator (line 886). It calls the Domoticz API with 'type=command¶m=getsettings' to retrieve global Domoticz settings and configuration.
    @mcp.tool()
    async def get_settings() -> str:
        """Get global Domoticz settings and configuration."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=getsettings")
            return response.text
  • The tool is registered using the @mcp.tool() decorator on line 886, which registers `get_settings` as an MCP tool with the FastMCP server instance.
    @mcp.tool()
  • There is also a corresponding MCP resource handler `get_settings_resource` registered as 'domoticz://settings' that provides the same Domoticz settings data via a resource URI.
    @mcp.resource("domoticz://settings")
    async def get_settings_resource() -> str:
        """Read global Domoticz settings and configuration."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=getsettings")
            return response.text
Behavior2/5

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

The description lacks explicit behavioral disclosure. Without annotations, it should state that the tool is read-only and safe. The word 'Get' implies retrieval but does not explicitly confirm no side effects or authorization requirements.

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, clear sentence with no redundant information. It earns its place by conveying the tool's purpose efficiently.

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

Completeness5/5

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

Given the tool's simplicity (no parameters, output schema present), the description is complete. It provides sufficient context for an AI agent to understand and invoke the tool correctly.

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?

With no parameters and 100% schema coverage, the description naturally adds no parameter info. The baseline for zero-parameter tools is 4, as no further elaboration is needed.

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 global Domoticz settings and configuration.' clearly states the action (get) and the resource (global Domoticz settings/configuration), distinguishing it from sibling tools like get_all_devices or get_system_status which retrieve different information.

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 is provided on when to use this tool versus alternatives. For instance, there is no mention that this is for general settings and that specific device or system queries should use other getters.

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