Skip to main content
Glama

getecoback-raumklima

wischwasser_getrenntes_gefaess_vor_folgetermin

Read-only

Ein bereits benutztes Wassergefäß für die nächste bestätigte Aufgabe nur nach dokumentierter Zustandsübergabe einplanen — Track whether the designated vessel is ready for a distinct next task.

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": {
      "termin_min": "<termin_min>",
      "fruehestens_min": "<fruehestens_min>",
      "vorbereiten_min": "<vorbereiten_min>",
      "wechselgefaess_passend": "<wechselgefaess_passend>",
      "zweckwechsel_geprueft": "<zweckwechsel_geprueft>"
    },
    "name": "wischwasser_getrenntes_gefaess_vor_folgetermin"
  }
}

Input Schema

NameRequiredDescriptionDefault
termin_minYesBeginn der nächsten Aufgabe am selben Tag.
fruehestens_minYesFrühester Beginn dokumentierter Vorbereitung.
vorbereiten_minYesGemessene Dauer der erlaubten Vorbereitung.
zweckwechsel_geprueftYesIst die nächste Handhabung des bisherigen Gefäßes für den anderen Zweck vollständig geklärt?
wechselgefaess_passendYesIst ein separat vorbereitetes passendes Gefäß verfügbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false, so safety and scope are clear. The description adds little beyond that: it does not explain what 'ready' means, what the tool returns, or how the documented handover condition affects the result.

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?

It is a single sentence with no obvious filler, but the structure is awkward: a long German clause comes first and is followed by an English restatement after an em dash. The bilingual duplication does not improve front-loading or clarity.

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?

This is a read-only check with five required parameters and no output schema, so the description should clarify the result and decision logic. Instead, it leaves the return value and readiness criteria unexplained, which is insufficient for an agent to invoke it confidently.

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 five parameters have clear schema descriptions, so the baseline is 3. The description itself does not add any parameter-level meaning or explain how the numeric and boolean inputs combine to determine readiness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a used water vessel and a next confirmed task, and says it tracks whether the vessel is ready. However, the mixed German/English phrasing blends 'einplanen' (planning/scheduling) with 'track whether' (readiness check), leaving the actual operation somewhat vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage condition is 'nur nach dokumentierter Zustandsübergabe' (only after documented state handover), which is a precondition but not guidance on when to choose this tool versus the many sibling vessel tools. No alternatives or exclusions are named.

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