Skip to main content
Glama

getecoback-raumklima

thermostat_service_zeitplan_wiederherstellung

Read-only

Vor einer vom Hersteller angeordneten Neueinrichtung feststellen, welche Zeitpläne danach überprüft werden müssen — Inventory heating schedules before a support-directed reconfiguration.

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": {
      "zeitplaene": "<zeitplaene>",
      "export_verifiziert": "<export_verifiziert>",
      "von_hand_notiert": "<von_hand_notiert>",
      "manuelle_bedienung_geprueft": "<manuelle_bedienung_geprueft>"
    },
    "name": "thermostat_service_zeitplan_wiederherstellung"
  }
}

Input Schema

NameRequiredDescriptionDefault
zeitplaeneYesAnzahl aktuell genutzter Zeitpläne.
von_hand_notiertYesZusätzlich ohne Export vollständig notierte Zeitpläne.
export_verifiziertYesDavon als lesbarer Export geprüft.
manuelle_bedienung_geprueftYesManuelle Bedienmöglichkeit dieses Modells vorab in der Anleitung geklärt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 meaningful framing that this is a non-destructive pre-check performed before a factory reset, but it says nothing about what the counts mean, whether any threshold changes the outcome, or what the agent should do with the result.

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?

Two sentences, front-loaded with the timing condition, but the German and English renderings are near-verbatim duplicates, so roughly half the text is redundant. The content itself is otherwise free of padding.

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 4-parameter tool with full schema coverage and no output schema, the description covers the when but not the decision logic: it does not say what combination of values constitutes 'ready to proceed' or what the caller should expect back, which is the main thing an agent needs here.

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 all four required fields individually documented (Anzahl genutzter Zeitpläne, notierte, export_verifiziert, manuelle Bedienung geprüft), so the schema carries parameter meaning. The description adds no interpretation of these values — notably it never explains how export_verifiziert relates to zeitplaene or why the manual-operation boolean matters to the decision.

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 action ('festellen, welche Zeitpläne ... überprüft werden müssen' / 'Inventory heating schedules') on a specific resource (heating schedules) and frames it as a pre-reconfiguration check, so an agent can tell it is a read-only assessment rather than a reconfiguration action. It does not explicitly distinguish itself from the many other thermostat/zeitplan siblings, and the tool name's 'Wiederherstellung' (restoration) sits slightly at odds with the described inventory purpose until the body clarifies it.

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 trigger is stated explicitly and up front: use this before a manufacturer- or support-directed re-setup ('Vor einer vom Hersteller angeordneten Neueinrichtung'). No when-not conditions or named alternatives are given, which keeps it short of a 5, but the temporal context is unambiguous.

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