Skip to main content
Glama

getecoback-raumklima

bad_feuchte_erholung_protokoll

Read-only

Gemessene Rückkehr in den eigenen Feuchtebereich nach einer Badnutzung bewerten — Check bathroom humidity recovery against the measured baseline.

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": {
      "vorher_rh": "<vorher_rh>",
      "spitze_rh": "<spitze_rh>",
      "spaeter_rh": "<spaeter_rh>",
      "minuten": "<minuten>",
      "toleranz_pp": "<toleranz_pp>",
      "aehnliche_temperatur": "<aehnliche_temperatur>"
    },
    "name": "bad_feuchte_erholung_protokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutenYesBeobachtungsdauer nach der Nutzung in Minuten.
spitze_rhYesErfasster Spitzenwert nach der Nutzung in Prozent.
vorher_rhYesRelative Feuchte vor der Nutzung in Prozent.
spaeter_rhYesRelative Feuchte nach dem selbst gewählten Beobachtungszeitraum.
toleranz_ppYesEigener Vergleichsbereich oberhalb des gemessenen Ausgangswerts in Prozentpunkten.
aehnliche_temperaturYesLufttemperatur am selben Sensorort vor und später hinreichend ähnlich?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the evaluation is against a measured baseline, which is useful behavioral context, but it does not explain what kind of verdict or comparison result the tool produces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the purpose, but the German and English clauses restate the same idea rather than adding complementary information. It is not bloated, but the bilingual duplication does not fully earn its place.

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

Completeness2/5

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

This is an evaluation tool with six required numeric inputs and no output schema. The description does not explain what the returned assessment looks like—whether it is a pass/fail verdict, a deviation value, or a protocol summary—which leaves an important gap for an agent invoking it.

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 all six parameters already have documented meanings and ranges. The description reinforces the baseline comparison idea but does not add syntax, units, or interpretation guidance beyond what the schema already provides, 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: evaluating measured humidity recovery after bathroom use against a measured baseline. It is clear enough to identify the tool's function, but it does not differentiate this tool from the many sibling humidity and ventilation tools.

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?

The phrase 'nach einer Badnutzung' implies the usage context: after a bathroom-use event with before, peak, and later humidity readings. However, it gives no explicit when-to-use guidance, no exclusions, and no alternative tools to prefer in other measurement scenarios.

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