Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_security_status

Retrieve the current status of your Domoticz security panel to monitor alarm state and security settings.

Instructions

Get the current status of the security panel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler (tool function) for get_security_status. It is decorated with @mcp.tool(), queries the Domoticz API with getsecstatus, and returns the result.
    async def get_security_status() -> str:
        """Get the current status of the security panel."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=getsecstatus")
            return response.text
  • The tool is registered with the MCP server via the @mcp.tool() decorator on line 1048, which is the standard FastMCP registration mechanism.
    @mcp.tool()
    async def get_security_status() -> str:
  • The docstring serves as the schema/description for the tool, which MCP uses to define its interface.
    """Get the current status of the security panel."""
Behavior2/5

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

Without annotations, the description is minimal and does not disclose behavioral traits like return type, authentication requirements, or what 'status' encompasses. The output schema exists but description should augment it.

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 with no wasted words: efficient and to the point.

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?

The output schema likely covers return values, and the description provides sufficient context for a simple getter with no parameters.

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?

No parameters exist, so the description does not need to add parameter meaning; baseline of 4 applies.

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 the current status of the security panel.' clearly identifies the tool's purpose with a specific verb and resource, distinguishing it from siblings like set_security_status.

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?

No guidance on when to use this tool versus alternatives; however, the simplicity of the tool (zero parameters) makes such guidance less critical.

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