Skip to main content
Glama

getecoback-raumklima

warmwasser_nutzwaerme_gegen_zaehler

Read-only

Gemischte Wasserentnahme mit einem zugehörigen Wärmezählerwert plausibilisieren — Compare useful draw heat with a thermal meter covering the agreed boundary.

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": {
      "mischvolumen_l": "<mischvolumen_l>",
      "hub_k": "<hub_k>",
      "zaehler_kwh": "<zaehler_kwh>",
      "gleiche_bilanzgrenze": "<gleiche_bilanzgrenze>"
    },
    "name": "warmwasser_nutzwaerme_gegen_zaehler"
  }
}

Input Schema

NameRequiredDescriptionDefault
hub_kYesTemperaturdifferenz gegenüber Kaltwasser in Kelvin.
zaehler_kwhYesWärmezählerdifferenz für denselben Zeitraum in kWh, kein Stromzähler.
mischvolumen_lYesVolumen des entnommenen Mischwassers in Litern.
gleiche_bilanzgrenzeYesGehört der Wärmezählerwert ausschließlich zum untersuchten Warmwasserbereich und Zeitraum?

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 non-mutating, local nature of the call is covered. The description adds that this is a comparison against a meter value over a shared boundary, but says nothing about what a plausibility result looks like, tolerance thresholds, or how mismatches are reported — and there is no output schema to compensate.

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 bilingual sentence, front-loaded with the action verb and the object of the comparison; nothing is redundant. The German/English duplication adds length but also disambiguates technical terms, so it is defensible rather than wasteful.

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 four-parameter, fully-documented, read-only check, the definition covers inputs and safety adequately. The notable gap is the outcome: with no output schema, the agent is not told whether the tool returns a boolean verdict, a deviation figure, or a text assessment, which matters for a plausibility-check 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%, with each of the four parameters explicitly documented (including the note that zaehler_kwh is a heat meter, not an electricity meter). The description's 'agreed boundary' phrasing reinforces gleiche_bilanzgrenze but adds no syntax or unit detail beyond the schema, so the 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 action (plausibilisieren / compare) and specific resources: the useful draw heat of mixed water versus a thermal meter reading. An agent can tell this is a cross-check tool rather than a pure calculation or cost comparison, though it does not name any sibling to contrast with.

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?

Usage is only implied: the phrase 'covering the agreed boundary' signals the precondition that both measurements must share the same system boundary, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative among the many warmwasser_* 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