Skip to main content
Glama

getecoback-climate-weather

luftbefeuchter_lokale_regelung_ersatzroutine

Read-only

Für die Übergabe klären, ob ein festes Feuchteziel am Gerät eingestellt oder separat kontrolliert werden muss — Distinguish a local target selector from a simple humidifier output setting.

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": {
      "bedienung": "<bedienung>",
      "hygrometer_vorhanden": "<hygrometer_vorhanden>",
      "anzeige_zugeordnet": "<anzeige_zugeordnet>"
    },
    "name": "luftbefeuchter_lokale_regelung_ersatzroutine"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedienungYesWofür gibt es am genauen Modell nachweislich eine lokale Einstellung?
anzeige_zugeordnetYesIst klar, ob die Anzeige Ziel, Messwert oder Leistungsstufe zeigt?
hygrometer_vorhandenYesSteht ein separates Hygrometer an einem geeigneten Messort zur Verfügung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the handover context and the substantive distinction to clarify, but it does not disclose what the tool returns, how it decides, or any other behavioral detail beyond what annotations and schema provide.

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?

The definition is brief and front-loads the core distinction before the English clarification. The bilingual phrasing is slightly redundant but not wasteful; every part contributes to understanding the decision at hand.

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 decision tool with no output schema, the description explains the decision context but omits what result or classification the agent should expect. The input schema is fully documented, so the main missing piece is return behavior and how the inputs combine into an outcome.

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%, with all three parameters documented in the input schema. The description adds no parameter-specific meaning, examples, or interaction logic beyond what the schema already states, so the baseline score of 3 is appropriate.

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 states a decision to make: whether a fixed humidity target is set on the device or must be controlled separately, and distinguishes a local target selector from a simple output setting. However, it is phrased as an instruction ('Für die Übergabe klären...') rather than a clear verb+resource action, and it does not explicitly say what the tool itself returns or does with that clarification.

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?

It mentions the context 'für die Übergabe' (for handover), which implies when it is relevant, but it provides no explicit when-to-use versus when-not-to-use guidance and does not reference or distinguish any alternative tools or procedures.

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