Skip to main content
Glama

getecoback-climate-weather

luftbefeuchter_modellpflege

Read-only

Dokumentierte Tankpflege und passende Verschleißteile nach exakter Befeuchter-Variante abrufen — Retrieve model-specific humidifier care and consumables.

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": {
      "model": "<model>"
    },
    "name": "luftbefeuchter_modellpflege"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesExakte Variante der deutschen Auswahl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety and scope are covered by structured data. The description adds only that results are 'dokumentiert' (documented) and model-bound; it says nothing about result shape, whether unknown models yield a fallback, or coverage limits of the care data.

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?

One compact sentence front-loading the resource and the scoping condition, duplicated bilingually without expanding content. The German/English duplication is redundant for a single-locale agent but not harmful.

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 simple: one fully documented enum parameter, read-only, no output schema. Still, the description never indicates what a caller gets back (care steps, part numbers, quantities) or how an 'unknown' model is handled, which an agent needs to interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with an enum whose description ('Exakte Variante der deutschen Auswahl') documents the parameter. The description reinforces that the model must be the exact variant, adding slight emphasis beyond the schema, but contributes no new syntax or selection rules for the 'unknown' value.

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?

States a specific verb ('abrufen'/'Retrieve') and resource ('Dokumentierte Tankpflege und passende Verschleißteile' / 'model-specific humidifier care and consumables'), scoped by exact humidifier variant. An agent can distinguish it from siblings like befeuchter_tank_laufzeit (runtime) or ersatzteil_druck_eignung (part pressure suitability) on topic grounds, though the definition names no sibling explicitly.

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?

Implicit guidance only: 'nach exakter Befeuchter-Variante' signals that the exact model must be known before calling, which matters given the 'unknown' enum value. There is no explicit when-to-use vs when-not, and no mention of what to do if the variant is not in the enum.

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