debmatic-mcp

List Devices

list_devices

Read-only

Identify HomeMatic devices by room, function, type, or name, and view their channels, types, and addresses. Find the precise device addresses required for value read and control operations.

Instructions

List all devices with their channels, types, and addresses. Optional filters: room, function, type, name. Use this first to discover device addresses for get_value/set_value.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Filter by device/channel name (substring, case-insensitive)
`room`	No	Filter by room name (exact match)
`type`	No	Filter by device type (exact match, e.g. 'HmIP-eTRV-2')
`target`	No	CCU target to read from (default: active). See list_ccu_targets.
`function`	No	Filter by function group name (exact match)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`devices`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.7.0Jul 4, 2026

addedInput schema / properties / target

Added value: +{
+  "description": "CCU target to read from (default: active). See list_ccu_targets.",
+  "type": "string"
+}

Changed1 schema field changedv1.3.0Jun 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "devices": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "required": [
+    "devices"
+  ],
+  "type": "object"
+}

First observedv1.1.2Jun 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint true, and the description adds detail on what is returned (channels, types, addresses), providing context beyond the annotations.

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?

Two sentences, front-loaded with main purpose, no wasted words. Efficient and clear.

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?

With an output schema (exists) and strong annotations, the description covers core functionality. Could mention return format but output schema handles it.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents parameters. The description adds a brief summary of filters but no new meaning, so baseline 3 is appropriate.

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 lists devices with channels, types, and addresses, and distinguishes it from siblings by mentioning discovery for get_value/set_value.

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?

Explicitly advises using this first to discover addresses for get_value/set_value, but does not specify when not to use it or compare to other listing tools like list_rooms.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.