Skip to main content
Glama

getecoback-raumklima

fenster_oberflaeche_taucheck

Read-only

Gemessene Innenscheibe auf Kondensation prüfen — Check an actual indoor glass or wall surface temperature against the indoor dew point.

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": {
      "room_c": "<room_c>",
      "room_rh_pct": "<room_rh_pct>",
      "surface_c": "<surface_c>"
    },
    "name": "fenster_oberflaeche_taucheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
room_cYesLufttemperatur innen in °C.
surface_cYesGemessene Temperatur der Oberfläche in °C.
room_rh_pctYesRelative Feuchte der Raumluft in Prozent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety is covered. The description adds that the check operates on actual measured values, but it says nothing about what the comparison yields (boolean risk flag, dew-point margin in K, recommendation) and no output schema exists to fill that gap.

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

Conciseness5/5

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

A single bilingual sentence, front-loaded with the German statement of purpose and followed by the English equivalent. No filler, no restated parameter names, and the scope qualifier appears immediately.

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 simple three-parameter read-only calculation with a fully described schema, the input side is complete. The output side is not: with no output schema, the agent cannot predict whether it receives a boolean, a temperature margin, or a formatted verdict, which matters for chaining into alerts or recommendations.

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% with units and ranges fully documented, so the baseline would be 3; the description adds modest extra meaning by stressing that surface_c is a measured value and may be a wall rather than only glass, clarifying intent beyond the field labels.

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 ('prüfen'/'check') and a precise comparison: measured surface temperature versus indoor dew point. It also clarifies that the surface may be glass or a wall, which separates it from pure U-value or solar-gain siblings, though it never names an alternative tool explicitly.

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?

Usage is only implied by the word 'Gemessene' — an agent can infer this tool is for real measurements rather than theoretical calculations, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many window/climate siblings.

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