Skip to main content
Glama

getecoback-raumklima

thermostat_handkorrekturen_versuchsfolge_notiz

Read-only

Auffälligen Wärmeverlauf bei manuell geänderten Vorgaben von einem wirklich unveränderten Vergleich trennen — Distinguish manually overridden comfort episodes from a clean baseline control.

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": {
      "versuche_gesamt": "<versuche_gesamt>",
      "ohne_eingriff": "<ohne_eingriff>",
      "ohne_eingriff_passend": "<ohne_eingriff_passend>",
      "nach_eingriff_passend": "<nach_eingriff_passend>"
    },
    "name": "thermostat_handkorrekturen_versuchsfolge_notiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
ohne_eingriffYesBlöcke ohne dokumentierten manuellen Eingriff.
versuche_gesamtYesZahl vergleichbarer vollständig protokollierter Arbeitsblöcke.
nach_eingriff_passendYesAndere Blöcke mit vollständigem Komforterfolg und dokumentiertem Eingriff.
ohne_eingriff_passendYesDavon Blöcke mit vollständigem persönlichem Komforterfolg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the conceptual distinction between overridden and clean baseline episodes, but it does not explain what the tool returns, how the comparison is performed, or any assumptions about the counts.

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 a single sentence and front-loads the core idea, but the German and English versions duplicate the same content, and phrases like 'wirklich unveränderten' add emphasis without precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has four required numeric inputs and no output schema, so the description should explain what result is produced or how to interpret the comparison. Instead it only restates the high-level distinction, leaving the agent without enough information to use the tool confidently.

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 all four numeric parameters are already documented in the schema. The description adds no additional meaning about how versuche_gesamt, ohne_eingriff, or the passend counts interact, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a conceptual purpose—separating manually overridden comfort episodes from a clean baseline—but it does not clearly say what operation the tool performs (calculation, note, comparison) or how it relates to its 'notiz' name. It is more specific than a tautology but remains vague about the actual action.

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 guidance on when to use this tool, when not to use it, or which sibling thermostat tools are alternatives. The description only implies a comparison scenario and leaves selection entirely to inference.

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