Skip to main content
Glama

getecoback-raumklima

trockner_ende_feuchte_stichprobe

Read-only

Ergebnis einer Trocknerladung gegen den geplanten Verwendungszweck einordnen — Check whether the observed dryness of the slowest-drying items suits the intended next step.

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": {
      "ziel": "<ziel>",
      "geeignet_bestaetigt": "<geeignet_bestaetigt>",
      "stichprobe_passend": "<stichprobe_passend>",
      "nur_programmende": "<nur_programmende>"
    },
    "name": "trockner_ende_feuchte_stichprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielYesGeplante Verwendung nach dem Trocknen.
nur_programmendeYesStützt sich die Angabe allein auf das Signal zum Programmende?
stichprobe_passendYesWurden die relevanten langsam trocknenden Stücke und dicke Stellen tatsächlich einbezogen?
geeignet_bestaetigtYesIst die gewünschte Restfeuchte am langsamsten trocknenden geprüften Stück beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear but thin. The description adds real behavioural content: the judgement must rest on the slowest-drying items and thick spots rather than the average load, and it is referenced to the planned next use. It stops short of saying what comes back (verdict, correction, follow-up recommendation) or how the tool behaves when nur_programmende=true undermines the claim.

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 and the purpose is front-loaded, but it is the same sentence twice, once in German and once in English, which is duplication rather than added information. The German verb 'einordnen' is noticeably vaguer than the English gloss 'Check whether…', so the second half is doing the disambiguating work the first half should have done.

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?

All four required parameters are documented at 100% coverage, so an agent can construct the call without help. However, there is no output schema, so the description arguably should say what the verdict looks like or what the caller should do with it, and it does not. For a pure judgement tool whose entire value is the returned classification, that is a real gap but not a fatal one.

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 every parameter carries a clear German description, so the schema already carries the semantics and the baseline is 3. The description only loosely mirrors two of the parameters ('slowest-drying items', 'intended next step') and adds no format, unit, or edge-case guidance beyond the schema. Nothing in the description corrects or enriches what the schema already states.

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 concrete operation on a concrete object: judge the outcome of a dryer load against the planned use, specifically asking whether the observed dryness of the slowest-drying pieces suits the next step. This is more specific than the German title alone and gives an agent a clear sense of the judgement being made. It does not distinguish this tool from near-neighbours such as trockner_programm_trockenmasse or waescheleine_trockner_ladeanteil, which is why this is not 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 tool is for the moment after a drying run, when an agent needs to decide if the load is ready for 'verstauen/buegeln/weiter_aufhaengen'. There is no explicit when-to-use/when-not, no mention of prerequisites (e.g. that a sample of the slow-drying items must actually have been checked), and no alternative tool is named. An agent must infer the context from the description.

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