Skip to main content
Glama

getecoback-climate-weather

thermostat_ventilabgleich

Read-only

Bekanntes Heizkörperventil gegen die geprüfte tado°-V3+-Kompatibilitätsliste abgleichen — Check a known radiator valve against reviewed tado V3+ records.

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": {
      "model": "<model>",
      "valve": "<valve>"
    },
    "name": "thermostat_ventilabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesThermostat-Generation aus der Geräteanleitung.
valveYesEindeutig identifizierter Ventilanschluss oder unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and closed-world scope are covered. The description contributes the fact that the comparison runs against *reviewed* records, i.e. curated rather than live data, but says nothing about what a match, partial match or miss looks like.

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?

A single front-loaded sentence with no wasted preamble, and the German/English mirroring helps a bilingual agent. The duplication is mildly redundant but costs little and does not obscure the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small two-enum read-only lookup the definition is close to sufficient, but there is no output schema and the description never says what the tool returns (compatible / not compatible / checklist detail). Given no output schema exists, that omission leaves the agent guessing about the result shape.

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 description coverage is 100% and both parameters are enums with per-value descriptions, so the schema carries the semantics. The description adds only the qualifier that the valve must be unambiguously identified; it does not explain how 'unknown' is treated in the result.

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 names a concrete verb (abgleichen/check) and a concrete resource (a known radiator valve) against a named reference (the reviewed tado V3+ compatibility list). No sibling in the list performs a compatibility lookup, so the agent can distinguish this tool from the cost/energy calculators without opening the schema.

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 word 'known' implies a prerequisite (the valve must already be identified before calling), which is useful implied guidance. However, it never states when to prefer this tool over e.g. the device-selection or cost siblings, and gives no exclusion or edge-case guidance (what to do when the valve is not on the list).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources