Skip to main content
Glama

getecoback-raumklima

entfeuchtung_rueckkehr_nach_pause

Read-only

Aus drei absoluten Feuchteproben den Anteil der Entfeuchtungswirkung bestimmen, der nach einer Gerätepause zurückgegangen ist — Report moisture rebound after a documented drying interval.

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": {
      "davor_g_m3": "<davor_g_m3>",
      "stop_g_m3": "<stop_g_m3>",
      "danach_g_m3": "<danach_g_m3>",
      "zeit_seit_stop_min": "<zeit_seit_stop_min>",
      "messung_vergleichbar": "<messung_vergleichbar>"
    },
    "name": "entfeuchtung_rueckkehr_nach_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
stop_g_m3YesAbsolute Feuchte am Ende der Entfeuchtung, in g/m³.
davor_g_m3YesAbsolute Feuchte vor dem Entfeuchten, in g/m³.
danach_g_m3YesAbsolute Feuchte am Ende der anschließenden Pause, in g/m³.
zeit_seit_stop_minYesAbstand zwischen Abschalten und letzter Probe in Minuten.
messung_vergleichbarYesAlle Proben am selben repräsentativen Messort, mit bewusst dokumentierter Nutzung und Fensterstellung?

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 state readOnlyHint=true and openWorldHint=false, and the description is consistent with a pure read-only computation. It adds the conceptual output ('share of drying effect that receded') but says nothing about result units, sign handling, or whether a 'danach' value above 'stop' yields a negative rebound — relevant behavioral detail for a calculation tool.

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?

A single compact sentence with a bilingual restatement; the core operation is front-loaded. The English clause is mildly redundant but functions as a gloss rather than padding.

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 five-parameter computation with no output schema, the description should convey what is returned and how edge cases are handled. It sketches the result concept but leaves the return shape, units, and treatment of implausible sample orderings unspecified.

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 per-field German descriptions of units and ranges, so the schema carries the parameter burden. The description only echoes 'three absolute moisture samples' and says nothing about 'zeit_seit_stop_min' or the comparability gate 'messung_vergleichbar', adding no meaning beyond the schema.

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 computation ('Anteil der Entfeuchtungswirkung bestimmen, der nach einer Gerätepause zurückgegangen ist') and the input basis (three absolute moisture samples), so an agent knows exactly what is calculated. It does not distinguish itself from any named sibling, but the operation is narrow enough to be unambiguous.

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 description implies the situation (a documented drying interval followed by a pause) but gives no explicit when-to-use rule, no conditions that would rule it out, and no alternative tool to pick instead. An agent must infer that this is only for post-pause rebound analysis and not for plain drying-performance checks.

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