Skip to main content
Glama

getecoback-raumklima

trockner_programmdauer_lastvergleich_lesen

Read-only

Stelle Label-Programmdauern nur für gleiche Lastbezüge gegenüber — Compare dryer label cycle duration only for matching loads

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": {
      "minuten_a": "<minuten_a>",
      "minuten_b": "<minuten_b>",
      "prueflast_a_kg": "<prueflast_a_kg>",
      "prueflast_b_kg": "<prueflast_b_kg>",
      "gleiches_programm_und_pruefverfahren": "<gleiches_programm_und_pruefverfahren>"
    },
    "name": "trockner_programmdauer_lastvergleich_lesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
minuten_aYesDokumentierte Programmdauer A in Minuten
minuten_bYesDokumentierte Programmdauer B in Minuten
prueflast_a_kgYesMasse der ausgewiesenen Prüfladung A in kg
prueflast_b_kgYesMasse der ausgewiesenen Prüfladung B in kg
gleiches_programm_und_pruefverfahrenYesGleiches Programmziel und Prüfverfahren dokumentiert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior2/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. The description adds only the matching-load rule and says nothing about what the call actually returns (a minute delta, a percentage, a pass/fail verdict) or how a mismatch is handled — is it a hard validation error or a note in the result? For a pure computation tool that ambiguity matters.

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 content is short and front-loaded, but the same sentence is given twice, once in German and once in English, with no additional information in the second pass. Half the text is pure duplication, so it earns conciseness points on length but loses them on redundancy.

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?

Five required numeric/boolean parameters, no output schema, and a domain-specific normative comparison — yet the description never indicates what the caller receives or how the two durations plus loads are combined. An agent knows the precondition but not the outcome shape, which is the main thing missing for a calculation tool.

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 every parameter (minuten_a/b, prueflast_a_kg/b_kg, the boolean) documented inline with units and bounds. The description's phrase 'gleiche Lastbezüge' loosely ties the prueflast parameters to the matching rule but adds no format, tolerance, or interpretation detail 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?

States a concrete verb (compare/gegenüberstellen) and a specific resource (Label-Programmdauern of a dryer), plus a scoping constraint ('nur für gleiche Lastbezüge'). An agent can tell this is a comparison of two documented cycle durations rather than a measurement or lookup. It does not differentiate itself from the many similarly named sibling 'lesen' tools.

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 description gives one implicit precondition — only compare when the load references match — which is reinforced by the required boolean 'gleiches_programm_und_pruefverfahren'. However, it never says what to do when loads do not match (skip the call? expect a rejection? return a warning?) and names no alternative tool for that 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