Skip to main content
Glama

getecoback-raumklima

heizwaesche_anfangsmasse_nassbezug_trockenbezug

Read-only

Gleich schwere Nassladungen mit unterschiedlichen trockenen Bezugsmassen vor einem Vergleich unterscheiden — Detect mismatched starting moisture in equally heavy wet loads.

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": {
      "bezug_gemessen": "<bezug_gemessen>",
      "a_nass_g": "<a_nass_g>",
      "a_trocken_g": "<a_trocken_g>",
      "b_nass_g": "<b_nass_g>",
      "b_trocken_g": "<b_trocken_g>",
      "nassspanne_g": "<nassspanne_g>",
      "wasser_spanne_g": "<wasser_spanne_g>"
    },
    "name": "heizwaesche_anfangsmasse_nassbezug_trockenbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_nass_gYesNasse Masse vor Versuch A.
b_nass_gYesNasse Masse vor Versuch B.
a_trocken_gYesTrockenreferenz für A.
b_trocken_gYesTrockenreferenz für B.
nassspanne_gYesGemeinsame Spanne zum Vergleich der Nassmassen.
bezug_gemessenYesLiegt für beide Wäschezusammensetzungen eine jeweils tatsächlich gewogene trockenheitsgleiche Referenz vor?
wasser_spanne_gYesGemeinsame Spanne zum Vergleich der anfänglichen Wasserüberschüsse.

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 safety and locality are covered. The description adds the meaningful behavioral framing that this is a gating/pre-check step rather than a measurement itself. It does not say what the tool produces (a verdict, a tolerance breach flag, numeric differences), which matters for a decision-style check.

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 text is short and front-loaded, but it is essentially the same sentence twice, once in German and once in English, so roughly half the content is duplication rather than added information. No wasted preamble, but also no structure that tells the agent what the tool returns.

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?

This is a seven-parameter, all-required decision tool with no output schema, so the description should explain what an agent gets back and how the tolerances are applied. It says nothing about the result shape or how the comparison outcome is expressed, leaving a real gap for invocation and interpretation.

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 each of the seven parameters documented in German (wet mass A/B, dry reference A/B, shared wet span, shared water span, and whether a weighed dry-equal reference exists for both). The description adds no interpretation beyond that, e.g. how nassspanne_g and wasser_spanne_g act as tolerances or how bezug_gemessen changes the evaluation. Baseline 3 is appropriate.

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 English half states a concrete check: detect mismatched starting moisture in equally heavy wet loads, i.e. distinguish two trials that look comparable by wet mass but differ in dry reference mass. That is a specific verb-plus-resource, and far more informative than the opaque German compound name. It does not differentiate itself from any of the many similarly named heizwaesche siblings, so it stops short of a 5.

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?

The phrase 'vor einem Vergleich' / 'before a comparison' implies the usage context: run this before comparing two wet-load trials to confirm their starting conditions are comparable. That is real, if implicit, guidance. There is no statement of when not to use it, what to do if the check fails, or which sibling handles the comparison itself.

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