Skip to main content
Glama

getecoback-climate-weather

duschwasser_mischverhaeltnis

Read-only

Warm- und Kaltwasseranteil für gemischtes Duschwasser aus gemessenen Temperaturen berechnen — Calculate hot and cold fractions at the shower mixer.

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": {
      "mixed_litres": "<mixed_litres>",
      "cold_c": "<cold_c>",
      "hot_c": "<hot_c>",
      "mixed_c": "<mixed_c>"
    },
    "name": "duschwasser_mischverhaeltnis"
  }
}

Input Schema

NameRequiredDescriptionDefault
hot_cYesWarmwasser am Mischer in °C.
cold_cYesKaltwasser am Mischer in °C.
mixed_cYesGemessene Mischtemperatur in °C.
mixed_litresYesGemischte Wassermenge in Litern.

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 the pure-calculation, side-effect-free nature is established. The description adds that the fractions are derived from measured temperatures, but does not say what the result looks like (fractions, percentages, or litre split) — and no output schema exists to fill that gap.

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 compact sentence with purpose front-loaded and no wasted clauses. The German/English duplication adds a little redundancy, but it is short enough that this does not hurt readability.

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 straightforward four-parameter calculation tool with a fully documented schema and read-only annotations, the description covers the essential purpose. Its remaining gap is the nature of the result, which neither an output schema nor the description clarifies.

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 all four parameters including units and valid ranges fully documented in the schema. The description only restates the concept of measured hot/cold/mixed temperatures and adds no format or constraint detail beyond the schema, so 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 states a specific verb and resource: calculating hot and cold water fractions at the shower mixer from measured temperatures. It is clearly distinguishable from flow-measurement siblings such as duschdurchfluss_messen, though it does not name any sibling explicitly.

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?

There is no when-to-use guidance, no prerequisites (e.g. that temperatures must be measured at the mixer), and no mention of when a different sibling tool would be the better choice. The agent must infer the usage context entirely from the purpose statement.

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