Skip to main content
Glama
jacedomotz

Domotz MCP Server

by jacedomotz

domotz_devices

Manage network devices on Domotz collectors: list, get, delete, hide, edit device details, view status and latency history, create remote connections, and more.

Instructions

Manage devices on Domotz collectors. Use the "action" parameter to select an operation. Most actions require agent_id and device_id.

ACTION REFERENCE:

  • list: List all devices on a collector (supports show_hidden, show_excluded filters)

  • get: Get single device details

  • delete: Delete a device

  • delete_down: Delete ALL down devices on a collector (only needs agent_id)

  • edit: Edit a device field (needs "field" param for the field name e.g. "importance", "details", and body with the new value)

  • hide: Hide a device from the dashboard

  • status_history: Device online/offline event history (filterable by from/to)

  • rtd_history: Round-trip delay (latency) time series (filterable by from/to)

  • connect: Create a remote connection to device (needs body with connection config)

  • onvif_snapshot: Get ONVIF camera snapshot image

  • uptime: Device uptime percentage (filterable by from/to)

  • monitoring_state: Set monitoring state (needs body)

  • applications: Applications running on a device (paginated)

  • count_applications: Count applications (lightweight HEAD request)

  • variables: Device variables (paginated, filterable by value/path/metric)

  • count_variables: Count device variables (lightweight HEAD request)

  • variable_history: Time-series for a specific device variable (needs variable_id)

GOTCHAS:

  • The "edit" action uses a "field" URL parameter to specify WHICH field to update (e.g. "importance", "details"), plus a body with the new value

  • count_applications/count_variables use HEAD requests and return {"count": N}

  • from/to accept ISO 8601 timestamps, default to last 7 days if omitted

  • delete_down deletes ALL down devices on the collector - use with caution

EXAMPLES:

  • List devices: {"action": "list", "agent_id": 5}

  • Get device details: {"action": "get", "agent_id": 5, "device_id": 200}

  • Device status history: {"action": "status_history", "agent_id": 5, "device_id": 42}

  • Latency history: {"action": "rtd_history", "agent_id": 5, "device_id": 99}

  • Device uptime: {"action": "uptime", "agent_id": 2, "device_id": 10, "from": "2025-01-01T00:00:00Z"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd time for time series
bodyNoRequest body (JSON object)
fromNoStart time for time series
nameNoFilter applications by name
pathNoFilter variables by path
fieldNoField name (for edit action)
valueNoFilter variables by value
actionYesThe operation to perform
metricNoFilter by metric
sort_byNoSort field for variables
agent_idNoAgent/Collector ID
device_idNoDevice ID
page_sizeNoMax items to return
device_idsNoFilter by device IDs
has_historyNoFilter by has_history
page_numberNoPage number, 0-indexed
show_hiddenNoInclude hidden devices in list
variable_idNoVariable ID
show_excludedNoInclude excluded devices (default: true)
sorting_directionNoSort direction (asc/desc)
Behavior5/5

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

With no annotations, the description fully carries the burden. It discloses that delete_down deletes ALL down devices, count_applications/count_variables use HEAD requests, from/to default to last 7 days, and edit uses a field URL parameter. These are critical behavioral details.

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

Conciseness4/5

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

The description is well-structured with sections: overview, ACTION REFERENCE, GOTCHAS, and EXAMPLES. It is somewhat lengthy but each section adds necessary context. Front-loading the purpose is effective.

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?

Given the complexity (17 actions, 20 params, no output schema), the description covers actions, required parameters, gotchas, and examples well. It does not detail return values, but the action reference and examples provide sufficient context for an AI agent.

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?

Schema coverage is 100%, but the description adds significant value by explaining each action's usage, the meaning of the 'field' parameter for edit, and that from/to accept ISO 8601 timestamps. It goes beyond the schema's basic descriptions.

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 'Manage devices on Domotz collectors' and lists all supported actions via the action parameter. It distinguishes this tool from sibling tools (e.g., domotz_agents, domotz_search_devices) by focusing on device-level operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an ACTION REFERENCE detailing which parameters are required for each action (e.g., 'list' needs agent_id, 'edit' needs field and body). It also includes a GOTCHAS section and examples. It does not explicitly contrast with sibling tools, but the scope is clear.

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/jacedomotz/domotz-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server