Skip to main content
Glama

getecoback-climate-weather

wasserkocher_portionsprobe_mindestmengenrest

Read-only

Bei einer schon gemessenen Getränkezubereitung überschüssige erhitzte Menge von der vorgeschriebenen Mindestfüllung unterscheiden — Separate mandatory fill surplus from additional measured excess.

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": {
      "erhitzt_ml": "<erhitzt_ml>",
      "benoetigt_ml": "<benoetigt_ml>",
      "minimum_ml": "<minimum_ml>"
    },
    "name": "wasserkocher_portionsprobe_mindestmengenrest"
  }
}

Input Schema

NameRequiredDescriptionDefault
erhitzt_mlYesBereits im vorgesehenen Kocher gemessene erhitzte Wassermenge.
minimum_mlYesDokumentierte Mindestfüllung für das exakt benutzte Modell und die Anwendung.
benoetigt_mlYesGemessene Menge für dieselbe Aufgabe, einschließlich beobachteter Verluste.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 agent knows this is a pure local computation with no side effects; the description correctly does not contradict that. It adds the precondition that the preparation has already been measured, which is genuine behavioral context. But it never explains how the three quantities combine (e.g. whether surplus is erhitzt minus max(minimum, benoetigt) or a separate residual), which is the one thing a caller most needs from a calculation tool.

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 single sentence is front-loaded and free of filler, so length is not the problem. However, the English half is a literal translation of the German half and contributes no new information, which is wasted space in a definition this short. Structure is acceptable but the bilingual duplication earns nothing.

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 bears the burden of explaining the return value — and it does not say what comes back or in what shape. Inputs are fully documented in the schema and the read-only nature is covered by annotations, so the omission of a return description is the single material gap. For a three-parameter calculation tool this leaves it only marginally adequate.

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 each parameter carries a precise German description (including 'einschließlich beobachteter Verluste' for benoetigt_ml), so the schema does the heavy lifting. The description's phrasing loosely maps 'überschüssige erhitzte Menge' to erhitzt_ml and 'vorgeschriebene Mindestfüllung' to minimum_ml, but adds no meaning about their relationship. Baseline 3 is appropriate.

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 does name a concrete operation (separating excess heated water from the prescribed minimum fill) and the precondition of an already-measured preparation, so the domain is identifiable. However, 'unterscheiden' is an abstract verb that never says what the tool actually produces — a surplus figure, a two-part breakdown, a verdict — so the agent cannot predict the result from the text. It also does not distinguish itself from the numerous other wasserkocher_* siblings.

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?

'Bei einer schon gemessenen Getränkezubereitung' implies a usage context: this applies once measurements already exist. That is a usable trigger condition but it is stated as a scene-setter rather than guidance. No alternative tool is named and no when-not condition is given, even though siblings such as wasserkocher_fuellsplitt_mindestmenge or wasserkocher_mehrmenge_szenario look adjacent in scope.

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