Skip to main content
Glama

getecoback-raumklima

thermostat_unauflosbare_kleine_stufen

Read-only

Zwei belegte benachbarte Einstellstufen darauf prüfen, ob sich beide am Arbeitsort trotz Messspielraum wirklich unterscheiden — Test whether measured desk temperatures resolve one documented control step.

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": {
      "stufe_niedrig_c": "<stufe_niedrig_c>",
      "stufe_hoch_c": "<stufe_hoch_c>",
      "platz_niedrig_c": "<platz_niedrig_c>",
      "platz_hoch_c": "<platz_hoch_c>",
      "gesamtspielraum_c": "<gesamtspielraum_c>",
      "zeitfenster_match": "<zeitfenster_match>"
    },
    "name": "thermostat_unauflosbare_kleine_stufen"
  }
}

Input Schema

NameRequiredDescriptionDefault
platz_hoch_cYesDort gemessenes Mittel bei höherer Einstellung.
stufe_hoch_cYesTatsächlich gewählte nächsthöhere Stufe in °C.
platz_niedrig_cYesUnter der niedrigeren Einstellung dokumentiertes Mittel am Nutzplatz.
stufe_niedrig_cYesTatsächlich gewählte niedrigere Stufe in °C.
gesamtspielraum_cYesBegründeter maximaler kombinierter Fehler der Differenz.
zeitfenster_matchYesGleicher Nutzungskontext und stabile, vergleichbare Messfenster?

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?

The annotations already establish that this is a read-only, non-open-world operation, and the description adds useful context about measurement tolerance and the comparison being performed. However, it does not explain the result semantics, decision threshold, or what output the agent should expect from the test.

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 description is short and front-loads the core test, with no unnecessary setup. The German and English versions duplicate the same content, which is mildly redundant but not harmful.

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?

With six required numeric/boolean inputs, full schema coverage, and read-only annotations, the definition gives enough to invoke the tool. However, there is no output schema and the description does not state what the test returns or how an unresolvable-versus-resolvable result is represented, which is a notable gap for a diagnostic 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 parameter meanings are already fully documented in the schema. The description reinforces that the tool compares two levels at the desk using a combined tolerance, but it adds no syntax, constraints, or interpretation beyond what the schema provides.

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 specific test: checking whether two documented adjacent thermostat setting levels are genuinely distinguishable at the desk despite measurement tolerance. It clearly identifies the resource and evaluation target, though it does not explicitly distinguish itself from the many sibling thermostat tools.

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?

The scenario is implied by the requirement for two documented adjacent setting levels and desk measurements, but there is no explicit 'use this when' guidance. No alternatives or when-not conditions are named, leaving selection among sibling thermostat diagnostics largely inferred.

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