Skip to main content
Glama

getecoback-climate-weather

entfeuchter_hygrostat_schaltband

Read-only

Feuchteband beim beobachteten Ein- und Ausschalten berechnen — Compare a dehumidifier’s observed switch-on and switch-off humidities with its setpoint.

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": {
      "switch_on_rh_pct": "<switch_on_rh_pct>",
      "switch_off_rh_pct": "<switch_off_rh_pct>",
      "setpoint_rh_pct": "<setpoint_rh_pct>"
    },
    "name": "entfeuchter_hygrostat_schaltband"
  }
}

Input Schema

NameRequiredDescriptionDefault
setpoint_rh_pctYesRelative Feuchte der Raumluft in Prozent.
switch_on_rh_pctYesRelative Feuchte der Raumluft in Prozent.
switch_off_rh_pctYesRelative Feuchte der Raumluft in Prozent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, and the wording 'berechnen'/'Compare' is consistent with a pure, side-effect-free computation. What the description does not disclose is what the computed band looks like (width only, deviation per threshold, a verdict?) — a real gap given there is no output schema.

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 short sentences, front-loaded with the computation before the comparison framing; nothing is padded. The German/English duplication is a slight redundancy but keeps each audience served in one line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-number, read-only calculation tool with full annotation coverage and no sub-objects, the definition supplies everything needed to invoke it correctly. The only unresolved item is the return shape, which is a minor omission for a simple arithmetic helper.

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 coverage is 100%, but all three parameters carry the identical boilerplate description 'Relative Feuchte der Raumluft in Prozent', so the schema does not distinguish the three roles. The description does assign roles (observed switch-on, observed switch-off, setpoint), which is a modest gain, but it adds no units nuance, ordering, or validity relations (e.g. switch-off typically below switch-on).

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 computation (the switching band / hysteresis) and its three ingredients — observed switch-on RH, observed switch-off RH, and setpoint RH — so the agent knows exactly what the tool does. It is distinguishable from sibling measurement checks like entfeuchter_ablaufcheck or entfeuchter_energie_je_liter, though it never explicitly contrasts itself with them.

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 only implied: you call it once you have observed both a switch-on and a switch-off humidity plus the device setpoint. There is no statement of when to prefer this over related dehumidifier diagnostics, no prerequisites, and no exclusions.

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