Skip to main content
Glama

getecoback-climate-weather

bad_heizgeraet_freigabe_unterlagen

Read-only

Für geplante Badheizung Modellunterlagen und fachliche Prüfung des konkreten Standorts erfassen — Identify missing bathroom-specific documentation before considering an electric heater.

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": {
      "modell_geeignet_dokumentiert": "<modell_geeignet_dokumentiert>",
      "ort_fachlich_geprueft": "<ort_fachlich_geprueft>",
      "befestigung_geprueft": "<befestigung_geprueft>"
    },
    "name": "bad_heizgeraet_freigabe_unterlagen"
  }
}

Input Schema

NameRequiredDescriptionDefault
befestigung_geprueftYesUntergrund und vorgesehene Befestigung wurden für genau diese Variante geprüft?
ort_fachlich_geprueftYesDer konkrete Standort und Anschluss wurden von einer Elektrofachkraft anhand örtlicher Anforderungen geprüft?
modell_geeignet_dokumentiertYesHersteller dokumentiert Verwendung im Bad für die genaue Variante?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 is covered and the description is not required to restate it. The description does add the useful framing that this is a gap-identification check, yet the verb "erfassen" (record/capture) sits in mild tension with readOnlyHint=true, and the description never says what the tool produces from the three answers. With annotations present the bar is lower, but this ambiguity keeps it at a 3.

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 tight clauses, front-loaded with the situation and ending with the actionable rule, with no filler. The German-then-English restatement is partly redundant, which keeps it from a 5, but each half contributes a slightly different nuance (what to capture vs. why).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-field, no-output-schema checklist gate, the description covers what the tool is for and when it applies, and the schema fully documents the inputs. The remaining gap is the verdict/return behavior: it never states that the three answers are combined into a pass/block or a list of missing documents, which an agent would want to know before calling it.

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 both enum parameters carry explicit German descriptions, so the input schema already explains each field fully. The description adds no parameter-level meaning beyond the fields it echoes in prose (model documentation, on-site verification), which is exactly the baseline-3 case where the schema does the heavy lifting.

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 verb+resource pair: capturing model documentation ("Modellunterlagen") and site-specific professional verification ("fachliche Prüfung des konkreten Standorts") for a planned bathroom heater. The closing clause "Identify missing bathroom-specific documentation before considering an electric heater" sharpens the intent into a documentation-gap check, so an agent can tell it is a gating checklist rather than a heater-sizing or BTU tool. It stops short of naming a sibling, but the purpose is unambiguous.

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 "before considering an electric heater" implies a sequencing rule (run this first, before evaluating heater options), which is useful context. However, no alternative tool is named, no exclusions are given, and it does not say what to do if documentation is already complete or what the next step is. Usage is implied rather than prescribed.

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