Skip to main content
Glama

getecoback-climate-weather

thermostat_betrieb_ohne_cloud

Read-only

Manuelle Bedienung und lokal gespeicherten Zeitplan eines Thermostats bei Internetausfall getrennt prüfen — Check documented offline controls independently of app or hub access.

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": {
      "genaue_variante": "<genaue_variante>",
      "manuell": "<manuell>",
      "zeitplan_lokal": "<zeitplan_lokal>",
      "zentralseitige_abhaengigkeit_geprueft": "<zentralseitige_abhaengigkeit_geprueft>"
    },
    "name": "thermostat_betrieb_ohne_cloud"
  }
}

Input Schema

NameRequiredDescriptionDefault
manuellYesManuelle Verstellung am Kopf ohne Internet laut Anleitung möglich?
zeitplan_lokalYesGespeicherter eigener Zeitplan ohne Internet funktionsfähig laut Anleitung?
genaue_varianteYesExakte Variante und Firmware oder Handbuchversion identifiziert?
zentralseitige_abhaengigkeit_geprueftYesAbhängigkeiten von Zentrale, Strom und Funk für den konkreten Aufbau separat geklärt?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds one genuinely useful behavioral note: it evaluates what is documented ("laut Anleitung") rather than probing a live device, and it insists on independent verification from app or hub. It says nothing about how the submitted findings are evaluated or what the caller gets back, and no output schema exists to fill that gap.

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 offline scope is front-loaded in the German clause and the English sentence restates the same intent compactly. The bilingual duplication costs a little space but adds no contradictions and no filler. No unnecessary context or hedging is present.

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?

This is a four-parameter, all-required assessment tool with no output schema, so the description should explain what a completed assessment yields or how the findings are judged. It covers the input side and the read-only framing adequately but leaves the outcome opaque. Adequate, not complete.

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 each of the four required parameters is documented in place, including enums for the two capability questions. The description only echoes the separation theme ("getrennt prüfen") and adds no format, ordering, or acceptance guidance beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 verb ("prüfen") and a specific resource pair ("manuelle Bedienung" and "lokal gespeicherter Zeitplan" of a thermostat), scoped to internet outage. It also clarifies the angle of the check ("documented offline controls ... independently of app or hub access"), which separates it from a live-probing sibling. It does not name any sibling explicitly, so it stops short of a 5.

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

Usage Guidelines4/5

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

The condition for use is stated plainly: when the internet is down, or when offline behavior must be assessed without app/hub access. "Getrennt prüfen" implicitly tells the agent to treat the two offline capabilities as separate checks. No explicit exclusions or named alternative tools are given, so it is clear context rather than full routing guidance.

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