debmatic-mcp

Get Values (Bulk)

get_values

Read-only

Retrieve datapoint values for multiple channels at once by specifying channel addresses, room, or function group.

Instructions

Read datapoint values for multiple channels at once via HM Script. Provide either a list of channel addresses, or filter by room or function name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_values"
  }
}

Input Schema

Name	Required	Description
`room`	No	Room name — read all channels in this room
`target`	No	CCU target to read from (default: active). See list_ccu_targets.
`channels`	No	Array of channel addresses to read
`function`	No	Function name — read all channels in this function group

Output Schema

Name	Required	Description	Default
`values`	Yes	One entry per channel: {address, name, datapoints}

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": {
+    "values": {
+      "description": "One entry per channel: {address, name, datapoints}",
+      "items": {},
+      "type": "array"
+    }
+  },
+  "required": [
+    "values"
+  ],
+  "type": "object"
+}

First observedv1.1.2Jun 11, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which cover safety and external calls. The description adds no additional behavioral context beyond what is in 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 efficient sentences front-load the verb and resource, with no wasted words. Every sentence serves a purpose.

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?

With an output schema present and clear description of input options (list or filter), the tool is well-documented for its complexity (4 optional params). No gaps.

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 each parameter has a description. The tool description adds context about the bulk operation and the 'HM Script' method, which adds meaning beyond the schema.

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 'Read datapoint values for multiple channels at once', using a specific verb and resource, and distinguishes from sibling tools like 'get_value' (singular) and 'get_paramset' (different purpose).

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 provides options for input (list of addresses or filter by room/function) but does not give explicit when-to-use or when-not-to-use guidance relative to alternatives. Usage is implied but not fully stated.

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