Skip to main content
Glama

getecoback-raumklima

wasserkocher_wahlstufe_abgleichen

Read-only

Gewünschten Sollwert mit dokumentierten Temperaturstufen des Wasserkochers vergleichen — Match a kettle target to a documented evenly spaced setting.

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": {
      "ziel_c": "<ziel_c>",
      "untergrenze_c": "<untergrenze_c>",
      "obergrenze_c": "<obergrenze_c>",
      "schritt_c": "<schritt_c>",
      "toleranz_c": "<toleranz_c>"
    },
    "name": "wasserkocher_wahlstufe_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_cYesGewünschter Sollwert in °C.
schritt_cYesEinheitlicher Abstand zwischen den Stufen laut Anleitung.
toleranz_cYesMaximal akzeptierte Abweichung der Einstellung vom gewählten Ziel.
obergrenze_cYesLetzte wählbare Stufe laut Anleitung.
untergrenze_cYesErste wählbare Stufe laut Anleitung.

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 state readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context by declaring that the settings are evenly spaced and documented, which implies step-based matching rather than free-form values. It does not disclose what happens when no setting falls within tolerance or whether the nearest or the first in-range setting is chosen.

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 filler. The bilingual restatement is mildly redundant but the German half alone already carries the meaning, so there is little wasted space.

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 read-only computation with five required, fully documented, non-enum numeric parameters, the description covers the input side adequately. However, with no output schema and no statement of what the result is (matched step, deviation, or pass/fail against tolerance), the agent cannot anticipate the return 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%, so the schema already explains all five parameters in German. The description adds only the framing that bounds and step describe a uniform documented ladder; it gives no extra detail on tolerance semantics or units beyond what the schema provides, so baseline 3 applies.

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?

The description states a specific verb (vergleichen/match) and resource (desired target vs. documented kettle temperature settings), and the 'evenly spaced setting' phrasing pins down the kind of matching being done. It does not explicitly distinguish itself from related siblings such as wasserkocher_warmhalte_schlussabgleich, but an agent can still tell what the tool does.

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 guidance, no prerequisites, and no named alternative or exclusion. The agent must infer from the name and parameters alone that this is for snapping a desired temperature onto a documented step ladder.

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