Skip to main content
Glama

getecoback-raumklima

wechselzeit_heiz_kuehl_schaltung

Read-only

Für einen Frühjahrs- oder Herbsttag den Abstand zwischen Heiz- und Kühlgrenzen und die daraus folgenden Messentscheidungen prüfen — Classify a mild-season morning, noon and evening against your chosen mode boundaries.

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": {
      "heizen_unter_c": "<heizen_unter_c>",
      "kuehlen_ueber_c": "<kuehlen_ueber_c>",
      "morgens_c": "<morgens_c>",
      "mittags_c": "<mittags_c>",
      "abends_c": "<abends_c>"
    },
    "name": "wechselzeit_heiz_kuehl_schaltung"
  }
}

Input Schema

NameRequiredDescriptionDefault
abends_cYesGemessene Raumtemperatur am Abend. In °C.
mittags_cYesGemessene Raumtemperatur am Mittag. In °C.
morgens_cYesGemessene Raumtemperatur am Morgen. In °C.
heizen_unter_cYesEigene Grenze für Heizbedarf. In °C.
kuehlen_ueber_cYesEigene Grenze für Kühlbedarf. In °C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 boundaries are user-chosen and that all three day segments are evaluated, but it never says what the classification result expresses (e.g., whether each segment is labeled heat/cool/neutral or only the threshold gap is reported).

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 content is front-loaded well, but the German and English halves largely restate each other, and the German phrase 'und die daraus folgenden Messentscheidungen prüfen' is vague padding. It could be halved without losing meaning.

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 five required parameters and no output schema, the description should describe the shape of the verdict (per-segment mode labels vs. a single gap value). It conveys the inputs and the general intent but leaves the expected return semantics undefined.

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 coverage is 100% with units, ranges and per-field descriptions, so the schema carries the parameter burden. The description reinforces that heizen_unter_c and kuehlen_ueber_c are the caller's own boundaries and that morgens/mittags/abends are the three evaluation points, but adds no ordering constraint (e.g., heating boundary must lie below cooling boundary).

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 action (prüfen/classify) on a specific resource: three time-of-day temperature readings judged against user-chosen heating and cooling thresholds. An agent can tell this is an evaluation/classification tool rather than a measurement or device tool, though it never distinguishes itself from any sibling.

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 opening 'Für einen Frühjahrs- oder Herbsttag' implies the usage context (mild-season days) and the English half repeats it as 'mild-season'. There is no explicit when-not guidance and no named alternative among the many sibling tools, so routing must be inferred from the season cue alone.

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