Skip to main content
Glama

getecoback-raumklima

befeuchter_nennwatt_abgabeleistung_bezug

Read-only

Erkenne, ob Feuchteabgabe und elektrische Leistung aus unterschiedlichen Betriebsstufen stammen — Check whether moisture output and rated watts share a 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": {
      "gemessene_wasserabgabe_ml_h": "<gemessene_wasserabgabe_ml_h>",
      "elektrische_leistung_w": "<elektrische_leistung_w>",
      "gleiche_stufe_bedingung": "<gleiche_stufe_bedingung>"
    },
    "name": "befeuchter_nennwatt_abgabeleistung_bezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
elektrische_leistung_wYesDokumentierte Leistungsaufnahme in W
gleiche_stufe_bedingungYesBeide Werte stammen aus derselben dokumentierten Stufe unter denselben Bedingungen
gemessene_wasserabgabe_ml_hYesDokumentierte abgegebene Wassermenge in ml/h

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 bar is lower. The description adds the semantic point that the tool is detecting mismatched operating stages, which is genuine context. However, it does not say what the tool returns or what the verdict means when gleiche_stufe_bedingung is false, leaving the outcome behavior opaque.

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 with the core check front-loaded and no filler. The bilingual duplication of the same statement is slightly redundant but aids disambiguation, and nothing in the text is off-topic.

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 three fully documented required parameters and read-only annotations, the input side is adequately covered. The significant gap is the absence of an output schema combined with no description of what the verdict looks like, so an agent cannot anticipate the result shape. For a pure judgement/check tool, the outcome semantics should have been stated.

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 the schema already documents all three parameters, including units and ranges. The description only loosely echoes two of them ('moisture output', 'rated watts') and alludes to the same-setting condition without adding syntax, format, or interpretation guidance. Baseline 3 applies since the schema is doing the heavy lifting.

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 description names a specific operation — verifying whether the moisture output figure and the electrical power figure originate from the same operating stage — rather than restating the tool name. An agent can tell this is a consistency/plausibility check over two documented values. It stops short of distinguishing itself from the many sibling humidifier/household-measurement checks, so a 4 rather than a 5.

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?

The text describes what the check is, but never says when to reach for it versus alternatives such as ab_haushaltsversuch_stoerfaktoren or the other befeuchter_* tools, nor what precondition must hold before calling. No exclusions or routing hints are provided; the agent must infer the trigger condition from the parameter names alone.

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