Skip to main content
Glama

getecoback-climate-weather

schrank_raumluft_feuchteunterschied_nach_umschichten

Read-only

Prüfe nach geänderter Schrankbelegung, ob der Abstand zum gleichzeitig gemessenen Raumwert kleiner wurde — Check whether a cupboard-to-room humidity gap narrowed after rearrangement

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": {
      "schrank_vor_rh": "<schrank_vor_rh>",
      "raum_vor_rh": "<raum_vor_rh>",
      "schrank_nach_rh": "<schrank_nach_rh>",
      "raum_nach_rh": "<raum_nach_rh>",
      "temperaturen_vergleichbar": "<temperaturen_vergleichbar>"
    },
    "name": "schrank_raumluft_feuchteunterschied_nach_umschichten"
  }
}

Input Schema

NameRequiredDescriptionDefault
raum_vor_rhYesErster zeitgleicher Raumwert
raum_nach_rhYesZweiter zeitgleicher Raumwert
schrank_vor_rhYesFrühere Ablesung am markierten Schrankpunkt
schrank_nach_rhYesSpätere Ablesung am selben Schrankpunkt
temperaturen_vergleichbarYesTemperaturen in den jeweiligen Messpaaren und die Aufstellhöhe sind vergleichbar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 description need not restate it. What the description omits is the salient behavior: what the tool returns (the two deltas? a verdict?) and what happens when temperaturen_vergleichbar is false — presumably a rejection, but that is left to inference.

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?

One front-loaded sentence with the action first and the scenario second, followed by an English restatement; nothing is padded. The bilingual duplication is mild redundancy given the name is already German, but it aids comprehension rather than hurting clarity.

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-required-parameter, annotation-covered read-only check with no output schema, the description conveys the operation but not the result shape or the failure mode of the comparability flag. An agent could call it correctly but would not know what to expect back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real conceptual meaning: the crowding of "gleichzeitig gemessenen Raumwert" and "Abstand" explains that the four humidity parameters form paired before/after measurements and that the quantity of interest is the cupboard-minus-room difference. It still does not interpret the temperaturen_vergleichbar gate, which is the parameter most likely to be guessed wrong.

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 states a specific verification action ("Prüfe ... ob der Abstand ... kleiner wurde") on a concrete resource pair: cupboard humidity vs. simultaneously measured room humidity, before and after rearrangement. That is far more specific than the name alone, though it never explicitly contrasts itself with the many sibling humidity-check 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 trigger condition is given implicitly and clearly — use it after a changed cupboard occupancy ("nach geänderter Schrankbelegung") when a before/after gap comparison is wanted. However, no exclusion or alternative is named, and the requirement that both readings come from comparable temperature conditions is only in the schema, not the description.

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