Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

get_event

Retrieve the source code and details of any Domoticz event script by providing its 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 main handler function for the 'get_event' tool. It takes an event_id parameter, calls the Domoticz API to load the event script, and returns its source code/details.
    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 'get_event' function is registered as an MCP tool via the @mcp.tool() decorator.
    @mcp.tool()
  • The schema/parameter definition for the 'get_event' tool: requires a single integer parameter 'event_id' and returns a string.
    async def get_event(event_id: int) -> str:
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It only says 'get' but doesn't disclose if it's read-only, any side effects, or return behavior beyond mentioning 'source code and details'.

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, no wasted words. Front-loaded with verb and resource.

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, description need not detail return values, but it's vague on what 'details' includes. Adequate for a simple retrieval tool but could be improved.

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%, and description adds minimal meaning beyond the parameter name 'event_id'. Doesn't explain what 'ID' refers to or how to obtain it.

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 'event script', and the method 'by ID'. It distinguishes from sibling tool 'get_events' which likely lists 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_events' or 'search_scripts'. No prerequisites or context provided.

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