Skip to main content
Glama

getecoback-raumklima

heizdecke_saison_vorlauf_abschaltcheck

Read-only

Ein dokumentiertes Vorwärmprogramm mit gewünschtem Ende vor der Nutzung abgleichen — Verify whether a documented blanket preheat timer ends before the chosen use time.

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": {
      "vorwaermen_ab": "<vorwaermen_ab>",
      "nutzung_ab": "<nutzung_ab>",
      "abschaltzeit_min": "<abschaltzeit_min>",
      "ablauf_bekannt": "<ablauf_bekannt>"
    },
    "name": "heizdecke_saison_vorlauf_abschaltcheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
nutzung_abYesBeginn der vorgesehenen Nutzung. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
vorwaermen_abYesGeplanter Beginn des Vorwärmprogramms. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
ablauf_bekanntYesDokumentiert die konkrete Anleitung dieses Vorwärmprogramm mit fester Abschaltung?
abschaltzeit_minYesFür gewählte Funktion verifizierte automatische Abschaltdauer. In Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 the safety profile is covered. The description adds nothing beyond restating the purpose, however — it does not say what happens when ablauf_bekannt is false, what the verdict looks like, or whether a margin/tolerance is reported. With no output schema, that gap is notable.

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?

One compact sentence, front-loaded with the action. However, the German and English halves are pure translations that convey no additional information, so half the text is padding rather than added value.

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?

All four parameters are required and fully documented in the schema, and the safety annotations are present, so an agent can call it. Still missing for a verification tool: what result form to expect and how the edge case of an undocumented program (ablauf_bekannt=false) is handled.

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% and every parameter carries a unit and range description, so the schema does the heavy lifting. The description contributes no additional meaning such as how the comparison is made or what the 2880-minute cap on Abschaltzeit implies. Baseline 3 applies.

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?

States a specific verb (abgleichen/verify) and resource (a documented preheat program's end time vs. the intended use time), which is more precise than the opaque tool name. It does not distinguish itself from the sibling heizstart_vorlauf_planen (planning vs. checking), so it falls short of a 5.

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?

Usage is only implied: the words 'dokumentiertes Vorwärmprogramm' and the required parameter ablauf_bekannt hint that this applies only when a documented timer exists, but there is no explicit when-to-use/when-not guidance or reference to alternatives.

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