Skip to main content
Glama

getecoback-raumklima

duschbereich_naesse_ausserhalb

Read-only

Wasser außerhalb des Duschbereichs anhand des Zeitpunkts zur Abklärung einordnen — Distinguish observations during use from water that reappears after the shower is off.

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": {
      "nur_beim_duschen": "<nur_beim_duschen>",
      "kehrt_ohne_entnahme_zurueck": "<kehrt_ohne_entnahme_zurueck>",
      "tritt_aus_fuge_oder_wand": "<tritt_aus_fuge_oder_wand>"
    },
    "name": "duschbereich_naesse_ausserhalb"
  }
}

Input Schema

NameRequiredDescriptionDefault
nur_beim_duschenYesWar die Nässe ausschließlich bei laufender Dusche sichtbar?
tritt_aus_fuge_oder_wandYesWar austretendes Wasser an einer Fuge, der Wand oder am Bodenübergang beobachtbar?
kehrt_ohne_entnahme_zurueckYesWurde die trocken gewischte Stelle ohne weitere Nutzung erneut nass?

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 this as read-only and not open-world, so the safety profile is covered. The description adds useful behavioral framing by explaining the diagnostic logic based on timing. It does not describe the return value or output categories, which is a notable gap for a classification tool with no output schema.

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?

The description is a single sentence, front-loaded with the core purpose and immediately followed by the distinguishing criterion. The English translation after the dash is slightly redundant but useful for multilingual contexts and does not add excessive length.

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 simple three-boolean diagnostic tool, the description covers what the tool does and how the inputs map to the diagnostic logic. However, with no output schema, it should explain what kind of result the tool returns (e.g., a category, recommendation, or clarification) to be fully complete.

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%, so all three boolean parameters are already fully documented with clear questions. The description reinforces the timing-based logic behind the parameters but adds no new syntax, constraints, or examples beyond what the schema provides. Baseline 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?

States a specific task: classify water outside the shower area based on timing, distinguishing water seen only during shower use from water that reappears after the shower is off. The verb 'einordnen' and the resource 'Wasser außerhalb des Duschbereichs' are clear. It does not name any sibling tool to differentiate itself, 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?

The phrase 'zur Abklärung einordnen' implies the tool is used when assessing observed water outside the shower area, giving an implicit usage context. However, it does not specify when not to use the tool, nor does it name or compare against any alternative diagnostic or leak-detection sibling.

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