Skip to main content
Glama

getecoback-climate-weather

luftbefeuchter_wasser_freigabe_beleg

Read-only

Wasserart für Beurer LB 200 oder LB 55 aus der genauen Anleitung bestätigen — Resolve a model-specific humidifier water claim.

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": {
      "modell": "<modell>",
      "wasser": "<wasser>"
    },
    "name": "luftbefeuchter_wasser_freigabe_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesBeurer-Artikel.
wasserYesBeabsichtigte Wasserart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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 essentially nothing beyond that: it does not say whether the result is a quoted manual passage, a confidence value, or a refusal for 'unbekannt' inputs, which is the main behavioral question for an evidence-lookup tool.

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?

It is short and front-loads the resource, but the bilingual split ('Wasserart für ... bestätigen — Resolve a model-specific humidifier water claim') duplicates the same vague idea twice without adding information, so the second half does not earn its place.

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?

With two fully enumerated required parameters, no nested objects, and no output schema, a short description is defensible, but an evidence/confirmation tool should at minimum state what it returns and how it treats unknown inputs. Those gaps leave it only minimally 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 both parameters carry enums with descriptions, so the schema already carries parameter meaning. The description only echoes the two model identifiers from the enum and says nothing about the 'unbekannt' option or the three water types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (Wasserart) and specific models (Beurer LB 200 / LB 55), but frames it as an instruction ('aus der genauen Anleitung bestätigen') rather than stating what the tool returns or does — the 'Beleg' (evidence record) aspect implied by the tool name is never explained. An agent can guess it confirms humidifier water guidance, but the verb is vague and there is no differentiation from sibling tools such as luftbefeuchter_modellpflege or befeuchter_tank_laufzeit.

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 named alternative. The presence of an 'unbekannt' value in both enums suggests the tool handles unknown-model/unknown-water cases, but the description never says whether it should be called in those cases or what happens then.

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