Skip to main content
Glama

getecoback-climate-weather

luftkuehler_verdunstungsgrenze

Read-only

Theoretische Verdunstungsgrenze aus Lufttemperatur und relativer Feuchte abschätzen — Estimate the wet-bulb limit for direct evaporative air cooling.

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": {
      "temperatur_c": "<temperatur_c>",
      "relative_feuchte_prozent": "<relative_feuchte_prozent>"
    },
    "name": "luftkuehler_verdunstungsgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
temperatur_cYesLufttemperatur am Einlass in °C.
relative_feuchte_prozentYesRelative Luftfeuchte am Einlass 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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety behavior is covered. The description adds that the result is a theoretical estimate, which is useful behavioral context, but it does not disclose output units, precision, or calculation limitations.

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?

The description is a single front-loaded bilingual sentence with no filler. The German statement and English gloss both directly serve the purpose without unnecessary wording.

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 simple read-only two-parameter calculation tool with full schema coverage and annotations, the description gives enough purpose and input context to invoke it correctly. The main remaining gap is that the output unit and precision are not stated, although 'wet-bulb limit' makes the return concept clear.

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%, and both parameters are already documented as inlet air temperature in °C and relative humidity in percent. The description names the same two inputs but adds no extra parameter semantics such as interpretation caveats or accepted range rationale.

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 verb, 'abschätzen/estimate', and a specific result, 'wet-bulb limit', for 'direct evaporative air cooling'. It is clear what the tool computes, though it does not explicitly differentiate itself from the many HVAC-related siblings.

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 direct evaporative air cooling' implies the appropriate context for use, but there is no explicit when-to-use/when-not guidance and no named alternative among the sibling tools.

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