Skip to main content
Glama

getecoback-raumklima

heizwaesche_messung_tara_vor_und_nach_wechsel

Read-only

Bei neuem Wiegekorb ein gemeinsam beobachtetes Zwischengewicht als Brücke verwenden — Reconcile two drying-log series through a same-mass anchor at a basket change.

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": {
      "uebergabe_gleichzeitig": "<uebergabe_gleichzeitig>",
      "alt_letzte_g": "<alt_letzte_g>",
      "neu_erste_g": "<neu_erste_g>",
      "spaeter_neu_g": "<spaeter_neu_g>",
      "vorher_alt_g": "<vorher_alt_g>"
    },
    "name": "heizwaesche_messung_tara_vor_und_nach_wechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
neu_erste_gYesZeitgleiche erste Brutto-Wägung im neuen Korb.
alt_letzte_gYesLetzte Brutto-Wägung im alten Korb.
vorher_alt_gYesFrühere Brutto-Wägung im alten Korb.
spaeter_neu_gYesSpätere Brutto-Wägung im neuen Korb.
uebergabe_gleichzeitigYesWurde dieselbe Netto-Masse am Übergang in beiden unveränderten Aufbauten direkt gewogen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a read-only, closed-world operation, so the safety profile is covered. The description adds real context by framing the computation as an anchor-based reconciliation requiring a jointly observed intermediate mass, but it says nothing about what is returned or how the result degrades when 'uebergabe_gleichzeitig' is false.

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 compact clauses with the condition front-loaded before the mechanism, so an agent gets the gist immediately. The German/English mirroring is mildly redundant, but it costs little and clarifies the domain jargon.

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 five-required-parameter computation with no output schema, the definition covers the input story adequately but leaves the return value entirely unexplained and does not state the consequence of a false simultaneity flag. An agent can call it, but cannot predict what it will get back.

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 coverage is 100%, so every one of the five parameters is already documented, which sets the baseline at 3. The description reinforces the role of the shared anchor (the 'gemeinsam beobachtetes Zwischengewicht' corresponding to the simultaneity flag) but adds no units, tolerances, or ordering 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 gives a concrete verb+resource: reconcile two drying-log series using a same-mass anchor observed at a basket change ('Bei neuem Wiegekorb ... als Brücke verwenden'). That is far more than a restatement of the name, though it never contrasts itself with near-neighbours such as the other container-change/tara tools, leaving differentiation to inference.

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 trigger condition is present and reasonably clear ('Bei neuem Wiegekorb' – only at a basket/container change), which is the main when-to-use signal. There is no explicit when-not guidance, no statement of what to do if the transition mass was not weighed simultaneously in both setups, and no named alternative for the ordinary same-basket case.

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