Skip to main content
Glama

getecoback-raumklima

betriebszustand_dokument_marktschnitt_setting_abweichung

Read-only

Den bei einem dokumentierten Softwarewechsel mitgeführten Stromsparmodus von anderen reinen Quellenänderungen unterscheiden — Compare actual saved timer settings across a verified revision without prescribing updates.

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": {
      "timer_vorher": "<timer_vorher>",
      "timer_nachher": "<timer_nachher>",
      "handbuch_davor_min": "<handbuch_davor_min>",
      "handbuch_danach_min": "<handbuch_danach_min>",
      "hardware_und_ziel_gleich": "<hardware_und_ziel_gleich>"
    },
    "name": "betriebszustand_dokument_marktschnitt_setting_abweichung"
  }
}

Input Schema

NameRequiredDescriptionDefault
timer_vorherYesVor der Revision bereits gespeicherter und belegter Zustand der Stromsparfunktion.
timer_nachherYesNach der Revision tatsächlich belegter gespeicherter Zustand.
handbuch_davor_minYesDokumentiertes Zeitfeld in der passenden vorherigen Anleitung.
handbuch_danach_minYesDokumentiertes Zeitfeld in der passenden späteren Anleitung.
hardware_und_ziel_gleichYesBeide Belege gelten für dieselbe Hardware, Zielart und beobachtete Revision?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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. The description adds that it will not prescribe updates and that it compares actual saved settings across a verified revision, but it does not explain output, permissions, or edge-case handling.

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?

It is a single front-loaded sentence with no filler. The bilingual German/English construction is dense and slightly redundant, but it remains compact and readable.

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?

Inputs are well covered by the schema, and annotations establish a safe read-only, closed-world operation. However, with no output schema, the description does not say what the comparison returns or how the distinction is represented, which is a meaningful gap for an analytical tool.

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 five parameters are fully documented in the schema, including the two enums and the 0–10080 minute bounds. The description adds little parameter-level meaning beyond mentioning timer settings and a verified revision.

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 gives a specific verb and resource — comparing actual saved timer settings across a verified revision and distinguishing a carried-over power-saving mode from pure source changes. It is clear what analytical check the tool performs, though it does not name a sibling alternative.

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

Usage Guidelines3/5

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

It supplies context (documented software change, verified revision) and an implicit boundary: it is for comparison, not for prescribing updates. It does not explicitly say when to choose this tool over the many sibling operating-state/document checks or name an alternative.

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