Skip to main content
Glama

getecoback-raumklima

kellerfeuchte_endlueftung_taupunkt_ursprung_wechseln

Read-only

Vergleiche Innen-Taupunkte nach zwei Lüftungsphasen relativ zum jeweils gemessenen Außenwert — Compare cellar recovery relative to the measured outdoor 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": {
      "innen_a_c": "<innen_a_c>",
      "aussen_a_c": "<aussen_a_c>",
      "innen_b_c": "<innen_b_c>",
      "aussen_b_c": "<aussen_b_c>",
      "pruefphasen_vergleichbar": "<pruefphasen_vergleichbar>"
    },
    "name": "kellerfeuchte_endlueftung_taupunkt_ursprung_wechseln"
  }
}

Input Schema

NameRequiredDescriptionDefault
innen_a_cYesInnen-Taupunkt am Ende der Phase A
innen_b_cYesInnen-Taupunkt am Ende der Phase B
aussen_a_cYesZeitgleicher Außen-Taupunkt zur Phase A
aussen_b_cYesZeitgleicher Außen-Taupunkt zur Phase B
pruefphasen_vergleichbarYesGleiche Messorte und vergleichbare Öffnungsphasen, Messpaare zeitgleich

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world read/comparison operation. The description adds useful context that the comparison is relative to measured outdoor dew points and framed as cellar recovery, but it does not describe the output, result interpretation, or what happens when the comparability precondition is false.

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?

The description is a single front-loaded sentence with no unnecessary procedural detail. The bilingual restatement is slightly redundant, but it does not obscure the core purpose.

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?

For a comparison/calculation tool with no output schema, the definition should explain what result is returned or how to interpret the comparison. The input schema and annotations are strong, but the description leaves a significant gap about the result and the effect of pruefphasen_vergleichbar.

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 five parameters are already documented in the input schema. The description adds a conceptual framing of two ventilation phases and relative outdoor measurements, but it does not add parameter-level meaning beyond the schema.

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 and resource: comparing indoor dew points after two ventilation phases relative to measured outdoor values. It is clear what the tool does, but it does not explicitly distinguish the tool from sibling dew-point comparison tools such as keller_taupunkt_reihenfolge_gepaart_vor_nach or taupunkt_lueften.

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?

The description implies the tool is for comparing two ventilation phases, but it gives no explicit guidance on when to use it versus alternatives or when not to use it. The precondition parameter pruefphasen_vergleichbar hints at a usage constraint, but the description does not discuss it.

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