Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_dewpoint_ventilation_advice

Calculate outdoor vs indoor/basement absolute humidity (g/m³) and dew point (°C) using Magnus-Tetens physics for mold-free ventilation and heat pump COP timing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_dewpoint_ventilation_advice"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name (e.g. Frankfurt, München, Berlin, London, New York)
cellar_rh_pctNoBasement relative humidity in % (default 68)
cellar_temp_cNoBasement temperature in °C (default 15.0)
indoor_rh_pctNoLiving room relative humidity in % (default 58)
indoor_temp_cNoLiving room temperature in °C (default 20.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the disclosure burden. It usefully reveals the computation method (Magnus-Tetens) and output quantities, establishing this as a deterministic read/compute operation, but it says nothing about needing network access for the city lookup, behavior on unknown cities, or why defaults exist for the four indoor/cellar inputs.

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 front-loaded sentence that states the computation, units, method, and application without filler. It is dense but every clause carries information; slight readability cost from packing physics and use-case into one line.

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 5-parameter, all-optional, read-only calculator with no output schema and full schema coverage, the description is nearly sufficient: inputs, units, and computed outputs are all identified. The residual gap is that the 'advice' implied by the tool name — the actual ventilation recommendation and how to interpret the outdoor/indoor comparison — is never described.

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 defaults documented inline, so the baseline is 3. The description adds one piece of meaning not in the schema: that 'city' supplies the outdoor side of the comparison while the cellar/indoor parameters supply the inside side, which clarifies how the five inputs relate.

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 gives a specific verb ('Calculate') and precise resources ('outdoor vs indoor/basement absolute humidity (g/m³) and dew point (°C)'), plus the physics method and intended outcome. It is unmistakable what the tool produces; the only gap is that it never states that outdoor values are sourced from live city weather data, which the 'city' parameter implies.

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 'for mold-free ventilation and heat pump COP timing' implies the decision contexts this tool supports, and no sibling tool overlaps in domain, so no explicit alternative routing is needed. However, there is no explicit when-to-use/when-not framing (e.g. 'use before opening windows', 'not for long-range forecasts'), leaving usage to inference.

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