Skip to main content
Glama
jacedomotz

Domotz MCP Server

by jacedomotz

domotz_power

Control device power actions and manage PDU outlets: list available actions, execute reboot/shutdown, and trigger outlet cycles with attach/detach device options.

Instructions

Manage device power actions and PDU power outlets. Use the "action" parameter to select an operation. Requires agent_id and device_id for all actions.

ACTION REFERENCE:

  • get_power_actions: List available power actions for a device (e.g. reboot, shutdown)

  • power_action: Execute a power action (needs "field" param with the action name from get_power_actions)

  • get_outlets: List power outlets on a PDU device

  • update_outlet: Update outlet settings (needs power_outlet_id + body)

  • trigger_outlet: Trigger an outlet action like cycle/on/off (needs power_outlet_id + outlet_action param e.g. "cycle", "on", "off")

  • attach_device: Attach a device to a power outlet (needs power_outlet_id + attached_device_id)

  • detach_device: Detach a device from a power outlet (needs power_outlet_id + attached_device_id)

GOTCHAS:

  • "trigger_outlet" uses "outlet_action" parameter (NOT "action") to specify what the outlet should do. The "action" param is always the tool operation selector.

  • "power_action" uses "field" parameter to identify which power action to execute

  • Workflow: get_power_actions first to see what's available, then power_action with the field name

EXAMPLES:

  • List power actions: {"action": "get_power_actions", "agent_id": 5, "device_id": 15}

  • List PDU outlets: {"action": "get_outlets", "agent_id": 5, "device_id": 15}

  • Cycle outlet: {"action": "trigger_outlet", "agent_id": 5, "device_id": 15, "power_outlet_id": 2, "outlet_action": "cycle"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body (JSON object)
fieldNoPower action field name
actionYesThe operation to perform
agent_idNoAgent/Collector ID
device_idNoDevice ID
outlet_actionNoOutlet action to trigger
power_outlet_idNoPower Outlet ID
attached_device_idNoDevice ID to attach/detach
Behavior5/5

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

With no annotations provided, the description fully covers behavioral aspects. It explains the purpose and prerequisites of each action, parameter usage, and potential pitfalls (e.g., 'field' param for power_action). The examples illustrate exact usage patterns.

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?

The description is well-structured with clear sections (ACTION REFERENCE, GOTCHAS, EXAMPLES). It is comprehensive yet concise, with every sentence adding value. The examples are minimal and illustrative.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, multiple actions, nested objects) and absence of an output schema, the description is remarkably complete. It covers all actions, parameter relationships, required fields per action, and common workflows.

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

Parameters5/5

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

Though input schema coverage is 100%, the description adds significant meaning beyond schema definitions. It explains the enum values for 'action', the purpose of 'field', 'outlet_action', and provides context for conditional parameters like 'attached_device_id'. The structured reference and examples clarify usage.

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 tool manages device power actions and PDU power outlets. It enumerates all specific actions (get_power_actions, power_action, etc.) and differentiates from sibling tools like domotz_agents and domotz_devices which cover different domains.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use advice for each action, including workflow guidance (e.g., call get_power_actions before power_action) and gotchas about parameter naming (outlet_action vs action). It also includes examples for several operations.

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