Skip to main content
Glama

getecoback-raumklima

thermostat_schaltfolge_platzband_asymmetrie

Read-only

Schaltpunkte einer stabil protokollierten Folge mit dem Zielband am persönlichen Nutzplatz abgleichen — Distinguish a documented late switch-on from late switch-off at the occupied spot.

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": {
      "platz_beim_ein_c": "<platz_beim_ein_c>",
      "platz_beim_aus_c": "<platz_beim_aus_c>",
      "platz_min_ziel_c": "<platz_min_ziel_c>",
      "platz_max_ziel_c": "<platz_max_ziel_c>",
      "echte_schaltfolge": "<echte_schaltfolge>"
    },
    "name": "thermostat_schaltfolge_platzband_asymmetrie"
  }
}

Input Schema

NameRequiredDescriptionDefault
platz_beim_aus_cYesDort gleichzeitig gemessener Wert genau beim nächsten Ausschalten.
platz_beim_ein_cYesAm Arbeitsplatz synchron beobachteter Wert genau beim Einschalten.
platz_max_ziel_cYesEigene obere Lufttemperaturgrenze am Arbeitsplatz.
platz_min_ziel_cYesEigene untere Lufttemperaturgrenze am Arbeitsplatz.
echte_schaltfolgeYesVollständige bestätigte Schaltfolge desselben Programms und unveränderte Messpositionen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 and the bar is lower. The description adds that the comparison is against the personal target band and that the result is a distinction between late switch-on and late switch-off, i.e. a directional diagnosis rather than a data dump. It does not indicate whether the tool returns a magnitude, a classification only, or how unusable input is reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and the goal is front-loaded, but it spends roughly half its length on a bilingual restatement that adds no new information. A single language with one added clause on the returned distinction would carry the same content more efficiently.

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 five-required-parameter analysis tool with no output schema, the description conveys the question being answered but not the shape of the answer, any tolerance or interpretation convention, or what happens when the sequence is flagged as not confirmed. Adequate but with clear gaps given there is no output schema to fall back on.

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% for all five parameters, including ranges and the meaning of the boolean confirmation flag, so the schema does the semantic work. The description adds no further interpretation of the on/off spot values versus the min/max target values beyond what the field descriptions already state; 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 names a concrete operation ('Schaltpunkte ... mit dem Zielband ... abgleichen') and a concrete diagnostic outcome ('Distinguish a documented late switch-on from late switch-off at the occupied spot'), which lets an agent tell it apart from the neighboring thermostat tools that deal with schedules, adapters or costs. The German noun stack ('stabil protokollierte Folge', 'Nutzplatz') is dense and the English half largely restates the German one, but the intent is recoverable.

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 explicit statement of when this tool should be chosen over a sibling, nor any exclusion. The only implicit precondition — a complete, confirmed switching sequence with unchanged measurement positions — lives in the parameter description rather than in the tool description, so the agent gets no routing guidance up front.

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