debmatic-mcp

Get Paramset

get_paramset

Read-only

Retrieve all parameters for a HomeMatic channel—runtime values, configuration, or a direct link's parameters—by addressing the channel or link partner.

Instructions

Read all parameters for a channel: VALUES (runtime state), MASTER (config), or a link paramset — for the latter pass the LINK PARTNER's channel address as paramsetKey (find partners with list_links). Interface is auto-resolved from the address.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>",
      "paramsetKey": "<paramsetKey>"
    },
    "name": "get_paramset"
  }
}

Input Schema

Name	Required	Description
`target`	No	CCU target to read from (default: active). See list_ccu_targets.
`address`	Yes	Channel address (e.g. '000A1BE9A71F15:1')
`interface`	No	Interface name override (auto-resolved if omitted)
`paramsetKey`	Yes	'VALUES', 'MASTER', or a link partner's channel address (reads that direct link's parameters)

Output Schema

Name	Required	Description
`params`	Yes	Map of parameter name → value
`address`	Yes
`paramsetKey`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.7.0Jul 4, 2026

changedInput schema / properties / paramsetKey / description

Previous value: -"Paramset to read"New value: +"'VALUES', 'MASTER', or a link partner's channel address (reads that direct link's parameters)"

removedInput schema / properties / paramsetKey / enum

Removed value: -[
-  "VALUES",
-  "MASTER",
-  "LINK"
-]

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": {
+    "address": {
+      "type": "string"
+    },
+    "params": {
+      "description": "Map of parameter name → value"
+    },
+    "paramsetKey": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "address",
+    "paramsetKey",
+    "params"
+  ],
+  "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?

The description reveals that the tool reads runtime state (VALUES), config (MASTER), or link params, and that interface is auto-resolved. Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds specific behavioral context without contradiction.

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 two sentences with no wasted words. It front-loads the core purpose and then adds the critical nuance about link paramsets. Every sentence serves a purpose.

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 has 4 parameters (2 required), an output schema exists, and annotations are present, the description covers the key aspects: the three paramset types, the special link partner case, and auto-resolution. It is sufficiently complete for an agent to use correctly.

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% (all parameters described), but the description adds extra meaning: it clarifies the paramsetKey values ('VALUES', 'MASTER', or a link partner's address) and confirms the auto-resolution of the interface parameter. This adds value beyond the schema definitions.

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 uses a clear verb ('read') and identifies the resource ('parameters for a channel'). It distinguishes three types of paramsets (VALUES, MASTER, link paramset) and explains the special usage for link paramsets via the paramsetKey field. This differentiates it from siblings like put_paramset.

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 implies usage by stating what the tool does and mentions using list_links to find partners, but it does not explicitly state when to use this tool versus alternatives (e.g., put_paramset for writing). There is no direct guidance on when not to use this tool.

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