Skip to main content
Glama

getecoback-raumklima

entfeuchter_geruch_eingrenzen

Read-only

Geruchszeitpunkt und sichtbare Hinweise beim Luftentfeuchter für die nächste Pflege- oder Serviceentscheidung einordnen — Triage dehumidifier odour with observation and manual-approved actions.

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": {
      "geruch": "<geruch>",
      "zeitpunkt": "<zeitpunkt>",
      "nach_pflege": "<nach_pflege>"
    },
    "name": "entfeuchter_geruch_eingrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
geruchYesBeobachteter Geruch.
zeitpunktYesWann tritt er vor allem auf?
nach_pflegeYesGeruch auch nach Reinigung der ausdrücklich zugänglichen Teile gemäß Anleitung vorhanden?

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 readOnlyHint=true and openWorldHint=false, and the description is consistent with a read-only triage/assessment. It adds the notion that resulting actions require manual approval, but does not explain what the triage produces (severity class, escalation flag) or what 'sichtbare Hinweise' refers to operationally.

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, front-loaded sentence with no filler. The German statement is then largely restated in English, which is mild redundancy but aids reach rather than hurting comprehension.

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?

The tool is small (3 required params, no output schema), and the description covers the input side adequately via the schema. Since no output schema exists, the description should say something about what the triage returns and what happens after 'manual-approved actions', which it leaves unstated.

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 coverage is 100% and both enums are self-describing, so the baseline is 3. The description gestures at two of the three inputs ('Geruchszeitpunkt', 'sichtbare Hinweise') but adds no interpretation of enum values, and 'sichtbare Hinweise' does not correspond to any parameter, which mildly blurs rather than clarifies.

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 a specific verb+resource combination: classify ('einordnen') dehumidifier odour using odour timing and visible signs, in service of a care-or-service decision. It is clear what the tool does, though it never distinguishes itself from odour- or maintenance-adjacent siblings such as entfeuchter_ablaufcheck or entfeuchter_tank_leerintervall.

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 'für die nächste Pflege- oder Serviceentscheidung' implies the decision context in which to call it, and 'manual-approved actions' hints at a follow-up workflow. There is no explicit when-not guidance and no named alternative tool for related checks, so the routing is only implied.

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