Skip to main content
Glama

getecoback-raumklima

entfeuchter_ablaufmeldung_schlauchsegmente

Read-only

Vorhandene Hinweise auf sichtbare Ablaufstrecke, Tank oder Pumpe zuordnen — Make a support note that distinguishes observed water paths from unknown sections.

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": {
      "ablaufart": "<ablaufart>",
      "verbindung_aussen_sichtbar": "<verbindung_aussen_sichtbar>",
      "wasser_ausserhalb_gefunden": "<wasser_ausserhalb_gefunden>",
      "ablaufende_sichtbar": "<ablaufende_sichtbar>"
    },
    "name": "entfeuchter_ablaufmeldung_schlauchsegmente"
  }
}

Input Schema

NameRequiredDescriptionDefault
ablaufartYesAktuelle Abführung nach der exakten Anleitung.
ablaufende_sichtbarYesBei einem Schlauch: Zielende von außen sichtbar?
verbindung_aussen_sichtbarYesAnschluss außen ohne Öffnen sichtbar?
wasser_ausserhalb_gefundenYesWasser wurde außen außerhalb des vorgesehenen Wegs beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the note distinguishes observed water paths from unknown sections, which is useful, but it does not explain whether a note is persisted, how conflicting observations are handled, or what evidence is required.

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 front-loaded, but the German and English clauses are not parallel: one describes assigning existing clues, the other describes making a support note. That bilingual restatement adds ambiguity rather than useful detail.

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 read-only four-parameter classification/reporting tool with no output schema, the description states the general outcome but not what the support note contains, how the booleans combine, or when to choose this over related checks. The schema descriptions fill parameter gaps, but usage context remains thin.

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?

All four parameters are fully described in the input schema, so the schema carries most parameter meaning. The description only loosely maps 'Ablaufstrecke, Tank oder Pumpe' to the ablaufart enum and mentions observed versus unknown sections; it adds little syntax or decision guidance 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?

The description names an action ('Hinweise ... zuordnen' / 'Make a support note') and the subject matter (visible drain path, tank or pump), and it clarifies the intended output distinction between observed water paths and unknown sections. It does not differentiate this tool from close siblings such as entfeuchter_ablaufcheck or entfeuchter_tankmeldung_uebergabe, and the 'Schlauchsegmente' aspect of the name is not reflected.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. 'Vorhandene Hinweise' weakly implies that prior observations should exist, but this is not developed into a usable routing rule.

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