Skip to main content
Glama

getecoback-climate-weather

befeuchter_weissen_belag_einordnen

Read-only

Weißen Belag nach Befeuchtertechnik und verwendeter Wasserart einordnen — Triage potential mineral residue from a humidifier without diagnosing its origin.

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": {
      "technik": "<technik>",
      "belag_ausserhalb": "<belag_ausserhalb>",
      "wasser_handbuchkonform": "<wasser_handbuchkonform>"
    },
    "name": "befeuchter_weissen_belag_einordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
technikYesGerätetechnik laut Handbuch.
belag_ausserhalbYesBelag auf Oberflächen nahe am laufenden Gerät bemerkt?
wasser_handbuchkonformYesWasserart laut Modellanleitung abgeglichen?

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, so the safety profile is covered. The description adds one genuinely useful behavioral caveat — that the result is a classification and not a diagnosis of origin — which prevents over-reliance. It says nothing about what the classification output looks like or how confident/limited it is.

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 compact sentence with the classifying verb front-loaded and the scope limitation appended. The bilingual phrasing is slightly redundant but adds little noise. No filler sentences.

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 three-parameter, fully-documented, read-only classification tool this covers purpose and scope adequately. With no output schema, however, the description never indicates what the triage result actually is (categories, verdict, caveats), leaving the agent unsure what to expect back. That gap keeps it at minimum-viable rather than 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% and two parameters carry enums, so the schema does the heavy lifting. The description echoes two of the three inputs (Befeuchtertechnik, Wasserart) but never mentions 'belag_ausserhalb', which is a key discriminator between residue on the device versus nearby surfaces. Baseline 3 is appropriate with no added semantics.

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?

Names a specific verb (einordnen/triage) and a specific resource (weißer Belag / mineral residue from a humidifier) conditioned on device technique and water type. The clause 'without diagnosing its origin' draws a clear scope boundary. It does not, however, distinguish itself from the sibling 'luftbefeuchter_weisser_belag', which a reader could easily confuse it with.

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 rather than stated: the tool is for triage, not for determining the cause of the residue. That gives an implicit when-to-use context, but no explicit when-not conditions and no named alternative for the diagnosis case. An agent must infer the routing itself.

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