Skip to main content
Glama

getecoback-climate-weather

luftbefeuchter_weisser_belag

Read-only

Weißen Belag nach Gerätetechnik und beobachtetem Auftreten einordnen — Check whether a white deposit may be linked to ultrasonic humidification.

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": {
      "technology": "<technology>",
      "appeared_during_use": "<appeared_during_use>",
      "water_known": "<water_known>"
    },
    "name": "luftbefeuchter_weisser_belag"
  }
}

Input Schema

NameRequiredDescriptionDefault
technologyYesIn der exakten Anleitung bezeichnete Gerätebauart.
water_knownYesWasserart und Härte überprüft und Freigabe des Herstellers bekannt?
appeared_during_useYesBelag bildet sich wiederholt während des Betriebs?

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 and the description does not need to restate it. What the description adds is the framing that this is a plausibility assessment ('may be linked'), which tells the agent the result is an appraisal rather than a measurement; however it says nothing about confidence, limits of the assessment, or what happens with non-ultrasonic technologies.

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?

Two compact clauses, resource first, with the German and English renderings roughly parallel. The bilingual duplication is somewhat redundant but serves disambiguation rather than padding, and there is no filler.

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 three-parameter assessment tool with no output schema, the definition should indicate what the classification yields (a verdict, a likelihood, a ranked set of causes). It does not, and it also leaves the relationship to the similarly named sibling unresolved, so an agent can invoke it but cannot fully anticipate the result.

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 parameters (technology enum, water_known, appeared_during_use) are already documented in the schema; the baseline of 3 applies. The description echoes 'Gerätetechnik' and 'beobachtetem Auftreten' but adds no interpretation beyond the schema and silently omits water_known, so no extra meaning is contributed.

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 German sentence names a concrete resource (weißer Belag) and a concrete operation (einordnen) qualified by two dimensions (Gerätetechnik, beobachtetes Auftreten), so the intent is legible. The English gloss narrows the same tool to 'ultrasonic humidification', which sits slightly at odds with the enum's broader technology set and, more importantly, with the near-identical sibling 'befeuchter_weissen_belag_einordnen', which the description never distinguishes.

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 framing 'Check whether a white deposit may be linked to ultrasonic humidification' implies a diagnostic/assessment use case, which is implied guidance. There is no explicit when-to-use or when-not-to-use statement, no prerequisites (e.g. water hardness data required), and no pointer to the very similarly named sibling that presumably serves a related but different classification purpose.

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