Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_event

Retrieve the source code and details of a Domoticz event script by providing its unique event ID.

Instructions

Get the source code and details of a specific event script by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_event' tool. It takes an event_id (int), makes an API call to Domoticz to load the event script source code, and returns the response text.
    async def get_event(event_id: int) -> str:
        """Get the source code and details of a specific event script by ID."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=events&evparam=load&event={event_id}")
            return response.text
  • The tool is registered with the MCP framework using the @mcp.tool() decorator on line 830.
    @mcp.tool()
  • The DomoticzClient helper class used by the handler to make authenticated HTTP requests to the Domoticz API.
    # Custom AsyncClient wrapper that ensures the token is added
    class DomoticzClient:
  • The _do_request helper function used by the handler to perform HTTP requests with OAuth retry logic.
    async def _do_request(client: httpx.AsyncClient, method: str, url: str, **kwargs) -> httpx.Response:
        """Perform a request with a single retry on 401 Unauthorized to handle expired tokens."""
        global _oauth_token_cache
        
        try:
            resp = await client.request(method, url, **kwargs)
            if resp.status_code == 401:
                # Token might be expired. Clear cache and retry once.
                _oauth_token_cache = None
                
                # Re-fetch token (this will trigger OAuth flow if needed)
                new_token = await _fetch_oauth_token(force_refresh=True)
                if new_token:
                    # Update headers for the retry
                    if "headers" not in kwargs:
                        kwargs["headers"] = {}
                    kwargs["headers"]["Authorization"] = f"Bearer {new_token}"
                    
                    # Retry the request
                    resp = await client.request(method, url, **kwargs)
            
            resp.raise_for_status()
            return resp
        except httpx.HTTPStatusError as e:
            if e.response.status_code == 401:
                raise Exception("Authentication failed. Please check your credentials or re-authenticate.")
            raise e
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it gets source code and details but does not disclose whether the operation is read-only, any permissions required, or error behavior (e.g., if event not found). Minimal behavioral context.

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 that is concise and front-loaded with the key action and resource. No redundant or extraneous information.

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

Completeness3/5

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

With an output schema present, return value details are not needed. However, the description lacks parameter guidance and usage context. Adequate for a simple getter with one parameter but could be enhanced.

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?

The input schema has one parameter 'event_id' with 0% schema description coverage. The description does not add any meaning beyond the parameter name; no format, range, or source references are provided.

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 verb 'Get', the resource 'source code and details of a specific event script', and the identifier 'by ID'. It effectively distinguishes from siblings like 'get_events' (list) and 'search_scripts'.

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 implies use when you have an event ID but provides no guidance on when to use this tool vs alternatives like 'get_events' or 'search_scripts'. No exclusion criteria or context about prerequisites.

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