Skip to main content
Glama

getecoback-climate-weather

heizkoerper_saison_warmefreigabe_pruefen

Read-only

Beim Herbststart den ersten Heizbedarf mit der zentralen Wärmeanforderung abgleichen — Trace the first heating demand through known room and central controls.

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": {
      "raum_fordert": "<raum_fordert>",
      "anlage_freigabe": "<anlage_freigabe>",
      "zentralanforderung": "<zentralanforderung>"
    },
    "name": "heizkoerper_saison_warmefreigabe_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
raum_fordertYesMeldet der Raumregler gerade Heizbedarf?
anlage_freigabeYesBeobachteter Status der zentralen Heizfunktion.
zentralanforderungYesWas zeigt die zugängliche zentrale Steuerung zur Wärmeanforderung?

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 declare readOnlyHint=true and openWorldHint=false, and the description reinforces that this is a diagnostic comparison rather than a configuration change. However, it does not describe what the check returns or how conflicting room and central states are interpreted.

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 autumn-start condition before the diagnostic action. The English sentence largely restates the German rather than adding new detail, but the overall text remains compact.

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 required inputs are fully specified in the schema and annotations cover the safety profile, so invocation is clear. With no output schema, however, the description does not explain what the check returns or how to interpret the combination of room demand and central status.

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 three required parameters are already documented with enums and descriptions. The description loosely maps them to room demand and central request but adds no format or interpretation details beyond the schema.

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 identifies a specific comparison at autumn start between first heating demand and central heat request, and the English clause clarifies tracing through room and central controls. The verb and resource are clear, though it does not explicitly differentiate this diagnostic from sibling heating checks.

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 'Beim Herbststart' provides a clear seasonal trigger for using the tool, but there is no explicit when-not guidance or mention of alternative diagnostics. This is usable context but falls short of routing guidance.

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