Skip to main content
Glama
adrighem

Domoticz MCP Server

by adrighem

send_notification

Send a notification to Domoticz notification subsystems with a subject and body to alert users about smart home events.

Instructions

Send a notification through Domoticz notification subsystems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYes
bodyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the send_notification MCP tool. It sends a notification through Domoticz by making a GET request to the Domoticz JSON API with the subject and body parameters URL-encoded.
    @mcp.tool()
    async def send_notification(subject: str, body: str) -> str:
        """Send a notification through Domoticz notification subsystems."""
        async with create_client() as client:
            response = await _do_request(client, "GET", f"{DOMOTICZ_API_URL}?type=command¶m=sendnotification&subject={urllib.parse.quote(subject)}&body={urllib.parse.quote(body)}")
            return response.text
  • The tool is registered using the @mcp.tool() decorator on the send_notification async function, which registers it with the FastMCP 'Domoticz' instance.
    @mcp.tool()
    async def send_notification(subject: str, body: str) -> str:
  • The input schema defines two string parameters: subject (the notification subject) and body (the notification body/contents). The return type is str.
    async def send_notification(subject: str, body: str) -> str:
Behavior2/5

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

With no annotations, the description should disclose behavioral traits such as whether the notification is sent immediately, what subsystems are used, or any side effects. It only states the basic action, leaving the agent unaware of important details.

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

Conciseness3/5

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

The description is a single sentence, which is concise, but it sacrifices necessary detail. It is appropriately front-loaded but fails to earn its place by providing substantive guidance.

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

Completeness2/5

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

Given the tool's simplicity and the presence of an output schema, the description should at least hint at what the response indicates. It does not, leaving the agent under-informed about the tool's full behavior.

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% and the description adds no information about the two required parameters 'subject' and 'body'. The agent gets no hints about expected formats, length limits, or content restrictions.

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 action ('Send') and resource ('notification') and specifies the context ('Domoticz notification subsystems'). It distinguishes from sibling tools which cover other actions like logging, device control, etc.

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. The description lacks any exclusions, prerequisites, or hints about appropriate contexts.

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