Skip to main content
Glama

getecoback-climate-weather

heizkoerper_kalt_pruefen

Read-only

Einen kalten Heizkörper anhand von Raumtemperatur und weiteren betroffenen Heizkörpern eingrenzen — Triage a cold radiator from observed room and radiator behavior.

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": {
      "room_warm_enough": "<room_warm_enough>",
      "other_radiators_work": "<other_radiators_work>",
      "gurgling": "<gurgling>"
    },
    "name": "heizkoerper_kalt_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gurglingYesIst Gluckern als zusätzliches Symptom hörbar?
room_warm_enoughYesErreicht der Raum seine gewünschte Temperatur?
other_radiators_workYesFunktionieren die anderen Heizkörper?

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 the useful framing that this is an inference from user-reported observations rather than a measurement, but it never says what the tool produces (a diagnosis, ranking of causes, or text) despite having no output schema.

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?

A single front-loaded sentence with no padding; the German original followed by an English gloss is mild duplication, but it aids cross-language agents and stays short. Nothing needs to be cut for clarity.

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 three required boolean/enum observation parameters, no output schema, and no annotations beyond read-only, the description should clarify what a triage call returns and how the symptom inputs combine. It covers the input premise adequately but leaves the result side entirely unaddressed.

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 parameters are already fully documented, and the baseline of 3 applies. The description echoes two of them (room temperature, other radiators) but says nothing about how the 'gurgling' symptom feeds the diagnosis, so it adds no meaning 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 states a specific action (eingrenzen / triage) on a specific object (a cold radiator) and names the evidence base (room temperature, other radiators). Within the sibling set, which is dominated by unrelated household diagnostics, this clearly identifies a radiator-fault triage tool, though it does not explicitly contrast with the one adjacent sibling (heizfuehler_standort).

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 word 'Triage' plus 'from observed room and radiator behavior' implies the use case: a radiator is cold and you want to narrow down the cause from observations. However, there is no explicit when-not guidance, no mention of prerequisites (e.g. system running, waiting time), and no named alternative such as a thermostat-location or heat-loss check.

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