Skip to main content
Glama

getecoback-raumklima

messbecher_zwei_marken_nutzteilung_abweichung

Read-only

Mit zwei kalten Wiegeproben prüfen, ob die Differenz benachbarter Messbecherstriche gleich groß ausfällt wie markiert — Check a measuring jug increment independently of absolute mark offsets.

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": {
      "marke_a_ml": "<marke_a_ml>",
      "marke_b_ml": "<marke_b_ml>",
      "wasser_a_g": "<wasser_a_g>",
      "wasser_b_g": "<wasser_b_g>"
    },
    "name": "messbecher_zwei_marken_nutzteilung_abweichung"
  }
}

Input Schema

NameRequiredDescriptionDefault
marke_a_mlYesNennmarke A des Bechers in ml.
marke_b_mlYesHöhere Nennmarke B in ml.
wasser_a_gYesBei separat tarierter kalter Probe an Marke A ermittelte Wassermasse in Gramm.
wasser_b_gYesEntsprechend ermittelte Wassermasse an Marke B in Gramm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered. The description adds that the measurement must be cold and separately tared, and that the comparison is relative rather than absolute, but it says nothing about what the tool returns or how a failing check is signalled.

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?

Two short clauses, method first, purpose second, with no filler. The German/English duplication costs a few words but is a deliberate translation convention rather than padding.

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-required-parameter, read-only computation with no output schema, the definition leaves a meaningful gap: an agent cannot tell whether the result is a boolean verdict, a deviation in ml, or a tolerance check. The input side is adequately covered by schema plus description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a real constraint the schema lacks: the two marks must be *adjacent* (benachbart), whereas the schema only calls B a 'higher nominal mark'. It also reinforces that both weighings are cold and separately tared.

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 concrete verb and object: use two cold weighing samples to check whether the difference between adjacent measuring-jug marks matches the printed increment. That is specific enough to distinguish it from the many other 'two-something' sibling tools, though it never names or contrasts a 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the phrase 'independently of absolute mark offsets' signals the case where absolute calibration is suspect, and 'zwei kalten Wiegeproben' implies the two-sample prerequisite. There is no explicit when-not guidance and no named alternative for checking absolute offsets instead.

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