Skip to main content
Glama

getecoback-climate-weather

spuelmaschine_temperatur_einlauf_abschnitte

Read-only

Bei dokumentiert geeignetem Wasseranschluss zwei geplante Zulaufabschnitte getrennt nach gemessener Wärmemenge erfassen — Estimate measured incoming water heat across two dishwasher fill segments.

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": {
      "a_l": "<a_l>",
      "a_anstieg_k": "<a_anstieg_k>",
      "b_l": "<b_l>",
      "b_anstieg_k": "<b_anstieg_k>",
      "warmwasser_eignung_belegt": "<warmwasser_eignung_belegt>"
    },
    "name": "spuelmaschine_temperatur_einlauf_abschnitte"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_lYesGemessene Liter der ersten Wasserentnahme.
b_lYesGemessene Liter der zweiten Wasserentnahme.
a_anstieg_kYesGemessener Temperaturabstand des ersten Zulaufs zu seinem bekannten Kaltbezug in K.
b_anstieg_kYesEntsprechender gemessener Temperaturabstand des zweiten Zulaufs in K.
warmwasser_eignung_belegtYesAnschlussart ist laut Anleitung für genau dieses Gerät und diese Messung geeignet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a read-only, non-open-world operation. The description adds the entry condition that suitability must be documented, which is useful context beyond the annotations, but it says nothing about how the two segments are combined, what the heat estimate represents, or what result is produced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The precondition is front-loaded, which is good structure, but the description duplicates the entire statement in German and English, which is wasteful for an agent that can read either. The two versions also use different verbs, adding noise rather than 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?

There is no output schema, so the description carries some burden of describing the return value. It implies a heat estimate but does not state the unit, the combination rule for the two segments, or the result format, which leaves a gap for a five-parameter computational 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%, so all five parameters are already documented in the input schema. The description confirms the two-segment structure and the heat-from-measurement intent but adds no new syntax, unit, or interpretation details beyond what the schema provides.

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 resource (two dishwasher inlet sections) and an operation on measured quantities (record/estimate heat from measured liters and temperature rise). However, it mixes 'erfassen' (record) with 'Estimate', which leaves the exact output slightly ambiguous, and it does not differentiate itself from siblings like spuelmaschine_warmzulauf_freigabe.

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?

A precondition is stated – the water connection must be documented as suitable ('Bei dokumentiert geeignetem Wasseranschluss') – which maps to the required warmwasser_eignung_belegt flag. There is no guidance on when not to use the tool, nor any named alternative among the many spuelmaschine siblings.

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