debmatic-mcp

Get System Info

get_system_info

Read-only

Get CCU system details: firmware, serial, addresses, active user role, and build info. Non-admin logins show N/A for restricted fields; unreachable targets return connection errors.

Instructions

Get CCU system information: firmware version, serial number, addresses. Reports the active login user and inferred role (ADMIN/USER) — note that version/serial/address are ADMIN-only on the CCU, so they show "N/A" for a non-admin (USER) login. A CCU that cannot be reached or logged into fails with that error instead — "N/A" always means "connected, not permitted". Also reports the running server's build identification (git branch/commit/tag and build time) under build.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`target`	No	CCU target to read from (default: active). See list_ccu_targets.

Output Schema

TableJSON Schema

Name	Required	Description
`role`	No	Access role inferred from which CCU methods answer: ADMIN if admin-only calls succeed, USER if logged in without admin rights. A CCU that cannot be reached or logged into raises that error instead of reporting a role
`user`	No	Configured login user for the active target
`build`	No	Build identification of the running server (stamped at build time)
`serial`	No	Serial number, or "N/A" if unavailable (ADMIN-only)
`target`	No	Active CCU target name
`address`	No	BidCos address, or "N/A" if unavailable (ADMIN-only)
`version`	No	Firmware version, or "N/A" if unavailable (ADMIN-only)
`accessNote`	No	Present when ADMIN-only fields are unavailable, explaining why
`cacheTypes`	No
`hmipAddress`	No	HmIP address, or "N/A" if unavailable (ADMIN-only)
`cacheWarming`	No
`serverVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv1.11.0Sep 2, 2026

removedOutput schema / properties / build / properties / branch / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / build / properties / branch / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / build / properties / builtAt / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / build / properties / builtAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / build / properties / commit / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / build / properties / commit / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / build / properties / describe / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / build / properties / describe / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / build / properties / dirty / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / build / properties / dirty / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedOutput schema / properties / build / properties / tag / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / build / properties / tag / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / role / description

Previous value: -"Access role inferred from which CCU methods answer: ADMIN if admin-only calls succeed, USER if logged in without admin rights, UNKNOWN if not connected"New value: +"Access role inferred from which CCU methods answer: ADMIN if admin-only calls succeed, USER if logged in without admin rights. A CCU that cannot be reached or logged into raises that error instead of reporting a role"

Changed11 schema fields changedv1.7.0Jul 4, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / target

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

addedOutput schema / properties / accessNote

Added value: +{
+  "description": "Present when ADMIN-only fields are unavailable, explaining why",
+  "type": "string"
+}

addedOutput schema / properties / address / description

Added value: +"BidCos address, or \"N/A\" if unavailable (ADMIN-only)"

addedOutput schema / properties / build

Added value: +{
+  "additionalProperties": false,
+  "description": "Build identification of the running server (stamped at build time)",
+  "properties": {
+    "branch": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Git branch (null if detached or not a git checkout)"
+    },
+    "builtAt": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "ISO timestamp of the build"
+    },
+    "commit": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Short commit SHA"
+    },
+    "describe": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "git describe --tags --dirty --always"
+    },
+    "dirty": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "true if the working tree had uncommitted changes at build time"
+    },
+    "tag": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Tag if HEAD is exactly on one, else null"
+    }
+  },
+  "required": [
+    "branch",
+    "commit",
+    "tag",
+    "describe",
+    "dirty",
+    "builtAt"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / hmipAddress / description

Added value: +"HmIP address, or \"N/A\" if unavailable (ADMIN-only)"

addedOutput schema / properties / role

Added value: +{
+  "description": "Access role inferred from which CCU methods answer: ADMIN if admin-only calls succeed, USER if logged in without admin rights, UNKNOWN if not connected",
+  "enum": [
+    "ADMIN",
+    "USER",
+    "UNKNOWN"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / serial / description

Added value: +"Serial number, or \"N/A\" if unavailable (ADMIN-only)"

addedOutput schema / properties / target

Added value: +{
+  "description": "Active CCU target name",
+  "type": "string"
+}

addedOutput schema / properties / user

Added value: +{
+  "description": "Configured login user for the active target",
+  "type": "string"
+}

addedOutput schema / properties / version / description

Added value: +"Firmware version, or \"N/A\" if unavailable (ADMIN-only)"

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": {},
+    "cacheTypes": {
+      "type": "number"
+    },
+    "cacheWarming": {
+      "type": "boolean"
+    },
+    "hmipAddress": {},
+    "serial": {},
+    "serverVersion": {
+      "type": "string"
+    },
+    "version": {}
+  },
+  "type": "object"
+}

First observedv1.1.2Jun 11, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds valuable behavioral context: ADMIN-only fields show 'N/A' for non-admin users, 'N/A' specifically means connected-but-not-permitted rather than unreachable, and connection/login failures return errors instead. This is exactly the kind of nuance an agent needs.

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 front-loaded with the core purpose and each sentence conveys meaningful operational detail. It is slightly long but justified because of the important 'N/A' vs. error distinction that cannot be safely omitted.

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, the description does not need to explain return values. It covers the tool's scope, permission-dependent behavior, and failure semantics, making it complete for an agent to invoke correctly.

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?

The single optional parameter 'target' is already fully described in the input schema with 100% coverage, including its default and pointer to list_ccu_targets. The description adds no additional parameter semantics, so the baseline of 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 uses a specific verb ('Get') and resource ('CCU system information'), then enumerates concrete contents: firmware version, serial number, addresses, active login user, role, and build identification. This clearly distinguishes the tool from siblings like get_connection_info and list_interfaces.

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 makes it obvious that this tool reads system information, and the input schema documents the default target. However, it does not explicitly state when to prefer this tool over alternatives like get_connection_info, nor does it give 'when not to use' guidance.

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