Skip to main content
Glama

getecoback-climate-weather

wasserkocher_zwei_arbeitsplaetze_verschiedene_volumen

Read-only

Zwei gleichzeitig angeforderte Mengen mit vorab geeigneten, unterschiedlich großen vorhandenen Behältern abgleichen — Assign two measured quantities to distinct approved serving vessels.

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_ml": "<a_ml>",
      "b_ml": "<b_ml>",
      "klein_ml": "<klein_ml>",
      "gross_ml": "<gross_ml>",
      "beide_geeignet": "<beide_geeignet>"
    },
    "name": "wasserkocher_zwei_arbeitsplaetze_verschiedene_volumen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_mlYesVon Arbeitsplatz A benötigte Menge in ml.
b_mlYesVon Arbeitsplatz B benötigte Menge in ml.
gross_mlYesNutzbare Menge des größeren geeigneten Gefäßes in ml.
klein_mlYesNutzbare Menge des kleineren geeigneten Gefäßes in ml.
beide_geeignetYesBeide Gefäße sind für die jeweilige Aufgabe und vorgesehene Temperatur geeignet.

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 safety profile is covered. The description adds the meaningful constraint that the vessels are 'vorab geeignete' (pre-approved and temperature-suitable), but it never says what happens when the two quantities cannot be accommodated, nor what form the 'Abgleich' result takes.

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 front-loaded sentence that states the core operation, with a bilingual gloss that aids disambiguation at minimal cost. There is no filler, though the duplicated German/English phrasing is slightly redundant.

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?

With no output schema, the description should clarify whether the tool returns an assignment, a feasibility verdict, or adjusted amounts — it does not. All inputs are documented via schema and the read-only nature is annotated, so the definition is workable but leaves the result semantics open for a decision-style 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 (a_ml, b_ml, klein_ml, gross_ml, beide_geeignet) are already documented in the schema. The description only restates the quantity/vessel pairing at a high level and adds no format, unit, or edge-case guidance beyond it.

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 concrete operation (reconciling two requested quantities against two differently sized, pre-approved vessels) and the English gloss 'Assign two measured quantities to distinct approved serving vessels' confirms the verb+resource. It is clear what the tool operates on, but it does not distinguish itself from near-siblings such as wasserkocher_zwei_aufguesse_servierplan or heissluft_zwei_mengen_zonenwahl.

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 statement of when this tool should be chosen over the many other two-quantity/two-vessel siblings, and no exclusions or preconditions are given. The agent must infer the use case entirely from the name and parameter list.

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