Skip to main content
Glama

getecoback-climate-weather

waschraum_uebergabebeutel_tara_einzeln_erfassen

Read-only

Bei geteilter Wäsche den zu übergebenden Teil ohne unterschiedliche Beutelgewichte nachvollziehen — Verify the net handover mass after independently taring both bags.

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": {
      "gleiche_charge": "<gleiche_charge>",
      "start_netto_g": "<start_netto_g>",
      "rueck_brutto_g": "<rueck_brutto_g>",
      "rueck_tara_g": "<rueck_tara_g>",
      "abgabe_brutto_g": "<abgabe_brutto_g>",
      "abgabe_tara_g": "<abgabe_tara_g>",
      "messspanne_g": "<messspanne_g>"
    },
    "name": "waschraum_uebergabebeutel_tara_einzeln_erfassen"
  }
}

Input Schema

NameRequiredDescriptionDefault
messspanne_gYesSelbst ermittelte kombinierte Messspanne.
rueck_tara_gYesGemessene Masse dieses leeren Beutels.
abgabe_tara_gYesGemessene Masse des leeren Übergabebeutels.
start_netto_gYesBekannte Netto-Ausgangsmasse der Gruppe bei gleichem Feuchtezustand.
gleiche_chargeYesSind Ausgangsgewicht, zurückbehaltener Teil und gemessene Übergabe derselben Gruppe zugeordnet?
rueck_brutto_gYesGemessene Bruttomasse des zurückbehaltenen Teils mit Beutel.
abgabe_brutto_gYesGemessene Bruttomasse der Übergabe mit anderem Beutel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint=true and openWorldHint=false annotations already tell the agent this is a side-effect-free, closed-world computation. The description adds genuine context beyond that: the two bags are tared independently and their differing bag weights are excluded from the net handover mass. It does not disclose failure behavior when "gleiche_charge" is false, nor the 20000 g bounds, which for a pure calculation tool with no annotations covering them would have been useful.

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 definition is short, but it is a single sentence duplicated verbatim across German and English, so half the text carries no new information. The operative clause ("after independently taring both bags") is buried at the end rather than front-loaded, and "ohne unterschiedliche Beutelgewichte" is elliptical enough to require re-reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 100% schema coverage and accurate no-side-effect annotations, the remaining burden is light. The description does not sketch the returned verification result, which matters slightly given the absence of an output schema. The description assumes the agent already knows the arithmetic being performed.

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 every one of the seven parameters is already documented in the schema, including the same-batch gate and the combined measurement span. The description only reinforces the framing that both bags are tared separately, mapping loosely onto abgabe_tara_g and rueck_tara_g; it adds no format, unit, or interaction detail beyond the schema. Baseline 3 applies.

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 names an operation ("Verify the net handover mass after independently taring both bags") and a context ("Bei geteilter Wäsche"), which is more specific than the tool name alone. However the verb "nachvollziehen"/"verify" never states that this is a computation over the supplied masses, nor what the verification produces, so an agent must infer the tool's actual function from the schema. No sibling tool is named or contrasted, so differentiation rests entirely on the path-like name.

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?

"Bei geteilter Wäsche" is the only situational hint and it is embedded mid-phrase rather than stated as a condition. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as the many other waschraum/abluft sibling tools. The agent must guess whether this applies to its case or whether another tool handles the same data.

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