Skip to main content
Glama

getecoback-raumklima

warmwasser_einmaliger_wasserweg_folge_nutzung

Read-only

Zwei tatsächlich beobachtete Verwendungen nach demselben Anlauf als eine Entnahme zählen — Avoid charging measured shared run-up twice across two immediate tasks.

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": {
      "entnommen_gesamt_l": "<entnommen_gesamt_l>",
      "anlauf_l": "<anlauf_l>",
      "nutzung_a_l": "<nutzung_a_l>",
      "nutzung_b_l": "<nutzung_b_l>",
      "genauso_gemessen": "<genauso_gemessen>"
    },
    "name": "warmwasser_einmaliger_wasserweg_folge_nutzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
anlauf_lYesDarin einmal erfasster Anlauf.
nutzung_a_lYesSeparat erfasste Teilmenge für die erste Verwendung.
nutzung_b_lYesSeparat erfasste Teilmenge für die zweite Verwendung.
genauso_gemessenYesWurde die Entnahme ohne weiteren unbemerkten Start und ohne doppelte Teilmessung erfasst?
entnommen_gesamt_lYesGemessene Gesamtentnahme für beide Verwendungen aus einer gemeinsamen Messung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world operation, and the description adds the key behavioral intent of preventing double-counting of a shared run-up. It does not explain the result, how the inputs are reconciled, or what happens when genauso_gemessen is false.

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?

The description is short and front-loads the core counting rule. The German sentence and English gloss are somewhat redundant, but there is no padding or unnecessary background.

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

Completeness2/5

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

For a five-required-parameter domain calculation with no output schema, the description is too thin. It does not clarify the expected result, the role of genauso_gemessen, or the handling of edge cases, leaving key invocation context unstated.

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 schema. The description reinforces the concepts of two uses and a shared run-up but adds no new syntax, constraints, or interpretation beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a domain rule: two observed uses after the same run-up should count as one withdrawal to avoid double-charging. However, it does not say what the tool actually does with the five inputs — compute, validate, or return a corrected volume — and it gives no differentiation from the many similar warm-water sibling tools.

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?

It implies the tool should be used when two uses share one run-up and the measured run-up should not be charged twice. There is no explicit when-to-use or when-not-to-use guidance, no named alternative, and no prerequisites for calling it.

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