Skip to main content
Glama

getecoback-climate-weather

camper_granulat_waegung_boxwechsel_tara

Read-only

Trenne die sichtbare Masseänderung einer Granulatbox vom Gewichtsunterschied zweier Behälter — Separate tare changes from observed mass gain in a winter absorber

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": {
      "gesamt_alt_g": "<gesamt_alt_g>",
      "tara_alt_g": "<tara_alt_g>",
      "gesamt_neu_g": "<gesamt_neu_g>",
      "tara_neu_g": "<tara_neu_g>",
      "inhalt_unveraendert_uebernommen": "<inhalt_unveraendert_uebernommen>"
    },
    "name": "camper_granulat_waegung_boxwechsel_tara"
  }
}

Input Schema

NameRequiredDescriptionDefault
tara_alt_gYesVorheriger leerer Behälter laut Wiegeprotokoll
tara_neu_gYesTara des später verwendeten Behälters
gesamt_alt_gYesVorher gewogene Gesamtmasse einschließlich Behälter
gesamt_neu_gYesSpäter gewogene Gesamtmasse einschließlich des verwendeten Behälters
inhalt_unveraendert_uebernommenYesDerselbe Inhalt vollständig übernommen, keine Entleerung oder Nachfüllung zwischen den Wägungen

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds that the operation isolates a confound ('sichtbare Masseänderung' vs. 'Gewichtsunterschied zweier Behälter'). It does not say what the corrected quantity is, how a false 'inhalt_unveraendert_uebernommen' affects the result, or whether any validation error is returned.

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?

It is a single front-loaded clause pair, but the German and English halves say essentially the same thing, so one of them is pure redundancy. The em-dash bilingual split also makes the sentence denser than it needs to be for a five-parameter calculation.

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?

There is no output schema, yet the description never states what the computation returns (a corrected mass delta? a tare-adjusted verdict?), which is the key missing piece for a pure calculation tool. It also leaves the handling of a false 'inhalt_unveraendert_uebernommen' flag unexplained, so the agent cannot predict behavior across all required-input combinations.

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 five parameters documented in German, so the schema does the heavy lifting and the baseline is 3. The description's phrasing loosely maps old/new total and tare readings to 'observed mass gain' and 'container difference', but adds no units, ordering, or edge-case semantics beyond the schema.

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 specific operation — separating the tare difference between two containers from the observed mass gain of a granulate box — with a clear verb ('Trenne' / 'Separate') and a concrete resource. It is intelligible as a tare-correction computation, though it never explicitly contrasts itself with the many sibling camper weighing tools.

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?

It states what is computed but not when to reach for this tool rather than a sibling (e.g. the stellvergleich or sättigungsintervall tools), nor any precondition beyond what the boolean parameter implies. The agent must infer the scenario (a box change occurred between two weighings) entirely from the parameter names.

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