Skip to main content
Glama

getecoback-raumklima

waesche_trocknung_teilserie_raumwechsel

Read-only

Prüfe, ob eine gewogene Wäscheladung nach dem Wechsel noch derselben Messreihe zugeordnet werden kann — Determine whether moved laundry still belongs to its original weigh-in series

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": {
      "masse_letzte_waegung_kg": "<masse_letzte_waegung_kg>",
      "masse_erste_waegung_kg": "<masse_erste_waegung_kg>",
      "waage_toleranz_kg": "<waage_toleranz_kg>",
      "ladung_unveraendert": "<ladung_unveraendert>"
    },
    "name": "waesche_trocknung_teilserie_raumwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
waage_toleranz_kgYesFür beide Wägungen gewählte gemeinsame Differenztoleranz in kg
ladung_unveraendertYesAlle Stücke und der Abzug des Behälters sind gleich geblieben
masse_erste_waegung_kgYesMasse direkt beim Beginn der zweiten Phase in kg
masse_letzte_waegung_kgYesWäschemasse am Ende der ersten Raumphase in kg

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds that this is a pure determination step, but says nothing about how tolerance and the unchanged-load flag interact to produce the verdict, nor about what happens when the check fails.

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 sentences with the core intent front-loaded and no filler. The bilingual duplication is mild redundancy but each version is compact and self-contained.

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?

With four required parameters fully documented and a read-only safety profile in annotations, the essentials are covered. However, there is no output schema, and the description never explains what the check returns (a boolean verdict, a tolerance comparison result, or an assignment identifier), which an agent needs in order to interpret the call.

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 all four parameters (both masses, the shared difference tolerance, and the unchanged-load boolean) are already documented in the schema. The description adds no extra meaning about how tolerances are applied or how the boolean gates the comparison, so the baseline of 3 applies.

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?

States a specific verb ('Prüfe, ob ... zugeordnet werden kann') and a precise resource: a weighed laundry load that has been moved between rooms and whether it still belongs to the original weigh-in series. The German sentence plus English gloss makes the intent unambiguous, but no sibling tool is named to sharpen the boundary against items like wasche_sammelwanne_zwei_tropfphasen_wechsel.

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 only implied: the word 'nach dem Wechsel' signals the room-change context in which this check applies. There is no explicit statement of when to call it versus alternatives, nor any prerequisite about when a re-weigh is required 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