Skip to main content
Glama

getecoback-raumklima

waescheleine_trockner_ladeanteil

Read-only

Eine gemischte Ladung nach vorliegender Trocknerfreigabe in Trockenwege aufteilen — Split the supplied dry load mass into dryer-permitted and separately dried laundry.

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_trocken_kg": "<gesamt_trocken_kg>",
      "trockner_freigegeben_kg": "<trockner_freigegeben_kg>",
      "trockner_limit_kg": "<trockner_limit_kg>"
    },
    "name": "waescheleine_trockner_ladeanteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_trocken_kgYesGesamte ursprüngliche Trockenmasse der Ladung in kg.
trockner_limit_kgYesProgrammbezogene Trockenmassegrenze des Trockners in kg.
trockner_freigegeben_kgYesTrockenmasse der ausdrücklich trocknergeeigneten Stücke 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 and the description does not contradict it. The description adds the meaningful behavioral detail that the split produces two categories (dryer-permitted and separately dried), but it says nothing about what the result looks like or whether the split respects the limit parameter, which is the crux of the operation.

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?

A single front-loaded sentence with the operation stated first, and the bilingual duplication is compact rather than padded. Nothing is wasted, though the German/English repetition adds length without adding information.

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?

There is no output schema, so the description carries the burden of explaining what is returned; it only implies two resulting mass portions without specifying shape, units, or rounding. For a small three-parameter pure-computation tool the definition is serviceable but leaves the return value underspecified.

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% and all three parameters are required and documented in the schema, so the baseline is 3. The description mentions the load mass and the dryer approval in prose but adds no semantics beyond what the schema already states about total mass, permitted mass, and the program-specific limit.

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 verb ('aufteilen' / 'split') and a specific resource (a mixed dry load, into dryer-permitted vs. separately dried portions). It is clearly a computation/partition tool rather than a lookup, but it does not differentiate itself from the many other trockner_* 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?

Usage is only implied: the phrase 'nach vorliegender Trocknerfreigabe' suggests it applies when a dryer approval and limit are already known. There is no explicit when-to-use, no exclusions, and no named alternative among the many sibling tools.

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