Skip to main content
Glama

getecoback-raumklima

waeschestaender_haube_versuchsbedingungen

Read-only

Versuche mit und ohne zugelassene Abdeckhaube auf vollständige Vergleichsbedingungen prüfen — Audit whether a cover-on/cover-off rack trial is comparable.

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": {
      "haube_freigegeben": "<haube_freigegeben>",
      "luftwege_frei": "<luftwege_frei>",
      "masse_gleich": "<masse_gleich>",
      "endzustand_gleich": "<endzustand_gleich>",
      "raumaufbau_gleich": "<raumaufbau_gleich>",
      "ohne_haube_min": "<ohne_haube_min>",
      "mit_haube_min": "<mit_haube_min>"
    },
    "name": "waeschestaender_haube_versuchsbedingungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
masse_gleichYesGleiche Textilien, Trockenmasse und vergleichbare Startfeuchte?
luftwege_freiYesWurden die geforderten Luftwege und Betriebsbedingungen eingehalten?
mit_haube_minYesGemessene Dauer mit Haube.
ohne_haube_minYesGemessene Dauer ohne Haube.
endzustand_gleichYesGleicher geprüfter Trockenzustand in beiden Durchgängen?
haube_freigegebenYesIst die Haube für das genaue Modell und die jeweilige Aufstellung freigegeben?
raumaufbau_gleichYesVergleichbare Raumtemperatur, Lüftung und zusätzliche Geräte?

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?

The readOnlyHint and openWorldHint=false annotations already tell the agent this is a safe, self-contained check. The description adds an audit framing that is consistent with those annotations, but stays silent on what a failed verdict implies, whether it blocks anything, or how the result is presented.

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 sentence pair with the verb and subject front-loaded and no filler. The German/English duplication is the only minor redundancy.

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 7-required-parameter audit tool the description is minimal, and the absence of an output schema means the agent gets no sense of the verdict format. The rich schema compensates for the parameter side, but the return behavior is left entirely opaque.

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 boolean/number parameter already carries a precise German explanation. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb (audit/check) and resource (cover-on vs cover-off rack trial comparability), and the bilingual phrasing makes the intent unambiguous. It doesn't differentiate against sibling rack tools by name, but a competent agent can still identify what this tool does.

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 implied: this is a pre-flight audit run before relying on a cover comparison trial. No explicit when-to-use or when-not-to-use guidance, and no named alternative tools, so the agent must infer the context.

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