Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_events

Get an overview of Domoticz's internal event system scripts and rules to inspect and manage your home automation logic.

Instructions

Get overview of the internal event system scripts and rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_events tool function - handler that fetches events list from Domoticz API with pagination support (offset/limit).
    @mcp.tool()
    async def get_events(offset: int = 0, limit: int = 50) -> str:
        """Get overview of the internal event system scripts and rules."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=events&evparam=list")
            events = response.json().get("result", [])
            paginated = _paginate(events, offset, limit)
            return json.dumps({"status": "OK", "result": paginated, "total_count": len(events), "offset": offset, "limit": limit})
  • The tool is registered via the @mcp.tool() decorator on line 821.
    @mcp.tool()
    async def get_events(offset: int = 0, limit: int = 50) -> str:
        """Get overview of the internal event system scripts and rules."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=events&evparam=list")
            events = response.json().get("result", [])
            paginated = _paginate(events, offset, limit)
            return json.dumps({"status": "OK", "result": paginated, "total_count": len(events), "offset": offset, "limit": limit})
  • The _paginate helper function used by get_events for pagination support.
    def _paginate(data: list, offset: int, limit: int) -> list:
        """Paginate a list of results."""
        return data[offset:offset + limit]
Behavior2/5

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

No annotations provided; the description implies a read operation ('overview') but does not explicitly state it is non-destructive or disclose any behavioral traits like authentication requirements or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is overly concise, consisting of a single sentence that lacks necessary detail. It is front-loaded but insufficiently informative.

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

Completeness1/5

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

Given the tool has an output schema and pagination parameters, the description is severely incomplete. It does not explain what the output contains, how to paginate, or any other contextual details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for descriptions, and the tool description does not mention the offset and limit parameters, leaving the agent unaware of pagination support.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it provides an overview of the internal event system scripts and rules, which distinguishes it from the singular get_event sibling. However, it could be more explicit about listing events.

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 get_event, create_event, or search_scripts. No mention of prerequisites or context.

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