Skip to main content
Glama

getecoback-climate-weather

thermostat_funkzentrale_abgleichen

Read-only

Vorhandene Funkzentrale mit einem dokumentierten Thermostat-System abgleichen — Match an existing hub to a documented smart radiator thermostat ecosystem.

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": {
      "modell": "<modell>",
      "hub": "<hub>"
    },
    "name": "thermostat_funkzentrale_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubYesVorhandene Zentrale.
modellYesDokumentiertes Thermostat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the safety profile is covered structurally. The description adds the useful nuance that the comparison is against a *documented* ecosystem rather than an open search, which explains the closed enum set. It does not say what happens on an unsupported pairing (e.g. 'andere-oder-keine') or whether the result is a verdict, a recommendation, or a config.

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?

Single short sentence, front-loaded with the action and the two operands. The German/English duplication adds length without new information, but it is compact and free of filler.

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 two-enum, fully documented, read-only lookup the description is nearly sufficient, and the annotations cover safety. The notable gap is the outcome: with no output schema, the description should say whether the tool returns a compatibility verdict, a missing-parts list, or a config recommendation, which an agent needs to decide whether to call it at all.

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% with both parameters enum-restricted and individually described ('Vorhandene Zentrale', 'Dokumentiertes Thermostat'), so the baseline is 3. The description reuses the same vocabulary ('Funkzentrale', 'dokumentiertes Thermostat-System') without adding format, precedence, or fallback semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: aligning ('abgleichen') an existing hub ('Funkzentrale') against a documented thermostat system, with the English sentence confirming the same. The agent knows this is a compatibility matching operation, though it does not explicitly distinguish itself from the neighbouring thermostat_* tools (amortisation, paketkosten, ventilabgleich).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no named alternative among the many thermostat_* and *_abgleichen siblings. The word 'dokumentiert' implies the tool only applies to documented combinations, but this constraint is left for the agent to infer rather than stated as a precondition.

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