Skip to main content
Glama

getecoback-raumklima

raumluft_wassermenge

Read-only

Wassermenge zwischen zwei Feuchtewerten in einem Luftvolumen berechnen — Estimate the grams of water in room air above a chosen relative humidity.

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": {
      "volume_m3": "<volume_m3>",
      "room_c": "<room_c>",
      "current_rh_pct": "<current_rh_pct>",
      "target_rh_pct": "<target_rh_pct>"
    },
    "name": "raumluft_wassermenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
room_cYesLufttemperatur innen in °C.
volume_m3YesLuftvolumen des Raums in m³.
target_rh_pctYesRelative Feuchte der Raumluft in Prozent.
current_rh_pctYesRelative Feuchte der Raumluft in Prozent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that the description adds almost nothing: it does not state that this is a pure physical calculation with no side effects, does not mention the underlying assumptions (e.g. standard air pressure, ideal-gas approximation), and does not clarify the sign/meaning of the result when target humidity is below current humidity.

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-loaded, but it is a bilingual duplication where the English half is a weaker paraphrase rather than new information. The second clause is arguably misleading (only one humidity level referenced) and forces the agent to reconcile two slightly different statements.

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

Completeness4/5

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

For a read-only, four-required-parameter calculator with a fully documented schema and no output schema, a one-line purpose statement plus unit hint is close to sufficient. The gaps are the physical assumptions and the meaning of the returned delta, which are useful but not strictly needed to invoke the tool correctly.

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 four parameters (volume_m3, room_c, current_rh_pct, target_rh_pct) are already documented in the schema with units and ranges. The description corroborates the two humidity thresholds and the air volume but never mentions room temperature, so it adds no meaning beyond the schema. Baseline 3 applies.

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 German clause gives a specific verb and resource: computing the water mass between two humidity values in a given air volume. The English gloss adds the output unit ('grams of water'), though its phrasing ('above a chosen relative humidity') only describes one threshold and is looser than the German. Purpose is clear, but no sibling tool is named or excluded.

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?

There is no statement of when to use this tool versus alternatives such as entfeuchter_energie_je_liter or befeuchter_tank_laufzeit, and no prerequisites are given. An agent must infer applicability from the description alone; the bilingual restatement consumes space that could have carried routing guidance.

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