Skip to main content
Glama
jacedomotz

Domotz MCP Server

by jacedomotz

domotz_inventory

Define inventory fields, assign values to devices, and manage custom tags. List device profiles and types to streamline network monitoring.

Instructions

Manage inventory fields, custom tags, device profiles, and device types. Use the "action" parameter to select an operation.

ACTION REFERENCE:

  • get_inventory: Get all inventory field definitions (no parameters needed)

  • delete_inventory: Delete all inventory fields (caution: removes all)

  • create_field: Create an inventory field (needs inventory_field name + body)

  • delete_field: Delete an inventory field (needs inventory_field name)

  • update_field: Update an inventory field (needs inventory_field name + body)

  • get_device_inventory: Get inventory data for a device (needs agent_id + device_id)

  • set_device_field: Set inventory field value on a device (needs agent_id + device_id + inventory_field + body)

  • delete_device_field: Clear inventory field on a device (needs agent_id + device_id + inventory_field)

  • get_tags: List all custom tags (no parameters needed)

  • create_tag: Create a custom tag (needs body)

  • edit_tag: Edit a custom tag (needs custom_tag_id + body)

  • delete_tag: Delete a custom tag (needs custom_tag_id)

  • bind_tag: Bind a tag to a device (needs agent_id + device_id + custom_tag_id)

  • unbind_tag: Unbind a tag from a device (needs agent_id + device_id + custom_tag_id)

  • get_device_tags: Get tags bound to a device (needs agent_id + device_id)

  • list_profiles: List all device profiles (no parameters needed)

  • apply_profile: Apply a profile to devices (needs device_profile_id + body)

  • list_base_types: List base device types (no parameters needed)

  • list_detected_types: List detected device types (no parameters needed)

EXAMPLES:

  • List all tags: {"action": "get_tags"}

  • Device inventory: {"action": "get_device_inventory", "agent_id": 5, "device_id": 42}

  • List device profiles: {"action": "list_profiles"}

  • List device types: {"action": "list_base_types"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body (JSON object)
actionYesThe operation to perform
agent_idNoAgent/Collector ID
device_idNoDevice ID
custom_tag_idNoCustom Tag ID
inventory_fieldNoInventory field name
device_profile_idNoDevice Profile ID
Behavior3/5

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

With no annotations, the description carries the burden. It mentions a caution for delete_inventory ('caution: removes all') and lists required parameters, but it does not disclose other behavioral traits like idempotency, side effects of each action, or authentication needs. More comprehensive disclosure would improve transparency.

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 an action reference and examples. It front-loads the purpose in the first sentence. While lengthy due to 19 actions, every section serves a purpose. Minor redundancy in 'needs' statements could be trimmed, but overall efficient.

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 tool's complexity (19 actions, 7 parameters) and no output schema, the description covers all actions, required parameters, and provides examples. It omits output details and error handling, but for a multi-action tool, it is fairly comprehensive.

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%, so baseline is 3. The description goes beyond by detailing which parameters are needed for each action (e.g., 'create_field: needs inventory_field name + body'), adding context that the schema alone lacks. This significantly aids tool invocation.

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 inventory fields, custom tags, device profiles, and device types,' which specifies the resource and action. This differentiates from sibling tools like domotz_devices or domotz_alerts, which focus on other domains.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives. The purpose is implied through the name and first sentence, but no direct comparison or exclusion criteria are provided. The sibling tools have distinct focuses, but guidance on switching between them is absent.

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