Skip to main content
Glama

getecoback-climate-weather

heizluefter_abschaltung_muster

Read-only

Normales Erreichen der Solltemperatur und auffällige Abschaltungen eines Heizlüfters auseinanderhalten — Triage observed portable heater shutdown 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": {
      "soll_erreicht": "<soll_erreicht>",
      "kippmeldung": "<kippmeldung>",
      "brandzeichen": "<brandzeichen>",
      "wiederholt": "<wiederholt>"
    },
    "name": "heizluefter_abschaltung_muster"
  }
}

Input Schema

NameRequiredDescriptionDefault
wiederholtYesAbschaltung wiederholt sich mit korrekter Aufstellung und weiter zu kaltem Raum?
kippmeldungYesGerät meldet Kippschutz oder steht nicht wie im Handbuch vorgesehen?
brandzeichenYesBrandgeruch, Rauch, auffällige Überhitzung oder beschädigter Stecker?
soll_erreichtYesSolltemperatur beim Abschalten erreicht?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety of the call is covered. The description adds that this is a triage/classification judgement rather than an action, which is useful, but it says nothing about what the triage returns, how urgently a 'brandzeichen' finding should be escalated, or what happens downstream — relevant gaps for a fire-risk assessment tool.

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 a bilingual gloss and no filler. It is appropriately short, though the bilingual restatement is slightly redundant and the structure leaves the triage outcome unstated.

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?

For a read-only tool with fully described required parameters and no output schema, the definition covers the inputs adequately but leaves the output side entirely implicit. An agent can call it correctly but cannot predict the shape or severity semantics of the result, which is a meaningful omission for a safety triage tool.

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 each of the four required parameters carries its own explanatory question in the schema, so the schema does the heavy lifting. The description adds no meaning about how the four answers combine into a verdict, which is the one thing the schema cannot express; 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?

The description names a specific operation — separating normal target-temperature cut-off from abnormal shutdown behaviour of a portable heater ('Normales Erreichen der Solltemperatur und auffällige Abschaltungen ... auseinanderhalten') — which is more specific than the tool name alone. It does not, however, distinguish itself from any sibling tool, so an agent must infer its niche from the name group.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'Triage' hints at a classification context, but the description states no explicit when-to-use, when-not-to-use, prerequisites, or alternative tool. Given the many sibling diagnostic tools, the agent gets no routing signal about which of them handles which fault class.

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