Skip to main content
Glama

getecoback-climate-weather

heizpause_raumfolge_wiederanlauf_engpass

Read-only

Nach gemeinsamer Absenkung zwei verschieden lange Wiederaufheizzeiten mit der Raumfolge prüfen — Check a shared restart against distinct readiness deadlines.

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": {
      "start_fruehestens": "<start_fruehestens>",
      "a_faellig": "<a_faellig>",
      "a_vorlauf": "<a_vorlauf>",
      "b_faellig": "<b_faellig>",
      "b_vorlauf": "<b_vorlauf>",
      "gemeinsam_geprueft": "<gemeinsam_geprueft>"
    },
    "name": "heizpause_raumfolge_wiederanlauf_engpass"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_faelligYesBeginn der Rückkehr in Raum A, in Minuten seit Mitternacht.
a_vorlaufYesGemessener Vorlauf in A.
b_faelligYesBeginn der Rückkehr in Raum B, am gleichen Tag.
b_vorlaufYesGemessener eigener Vorlauf in B.
start_fruehestensYesFrühester verfügbarer Start nach Ende der Absenkung.
gemeinsam_geprueftYesWurden beide Vorläufe beim gleichzeitigen Heizbeginn beobachtet?

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 the operation is a comparative check against 'distinct readiness deadlines' rather than a mutation. It does not say what a failed check means, whether the result is a bottleneck verdict or a sequence order, or what happens when the earliest start cannot satisfy both deadlines.

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?

Two compact clauses, one German and one English, with the precondition front-loaded before the operation. The bilingual restatement is slightly redundant but does not pad the definition or bury the key information.

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 parameters, no output schema, and a name invoking 'Engpass' (bottleneck), the agent still lacks any indication of what the call returns or how the two deadline comparisons are resolved. The description is adequate to identify the operation but leaves the result shape and the meaning of a detected bottleneck undocumented.

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 six parameters (a_faellig, a_vorlauf, b_faellig, b_vorlauf, start_fruehestens, gemeinsam_geprueft) are already documented at the field level. The description reinforces the pairing idea ('zwei verschieden lange Wiederaufheizzeiten', 'gemeinsam') but adds no units, constraints, or relation semantics beyond what the schema states.

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 concrete operation ('zwei verschieden lange Wiederaufheizzeiten mit der Raumfolge prüfen') and its trigger condition ('nach gemeinsamer Absenkung'), so an agent can tell this is a two-room restart-feasibility check. It stops short of declaring how it differs from the closely named sibling heizpause_durchlaufen_wiederaufheizen, so it is clear but not fully disambiguated.

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 phrase 'nach gemeinsamer Absenkung' establishes the situation in which the tool applies, which is genuine when-to-use context. There is no statement of when not to use it, no prerequisites, and no named alternative for the single-room or continuous-reheat case, leaving routing 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