Skip to main content
Glama

getecoback-climate-weather

klima_nachstroemwaerme_schaetzen

Read-only

Fühlbare Wärmelast durch nachströmende Außenluft bei einem Abluftgerät berechnen — Estimate sensible heat gain from outdoor makeup air.

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": {
      "aussenluft_m3_h": "<aussenluft_m3_h>",
      "innen_c": "<innen_c>",
      "aussen_c": "<aussen_c>"
    },
    "name": "klima_nachstroemwaerme_schaetzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
innen_cYesInnenlufttemperatur in °C.
aussen_cYesTemperatur der nachströmenden Außenluft in °C.
aussenluft_m3_hYesTatsächlich angenommener Außenluftanteil der Nachströmung in m³/h.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 the agent knows this is a closed-domain, side-effect-free computation; the description adds the useful scoping detail that only the makeup-air share is being estimated. It does not disclose the output quantity or unit (W vs. kW), whether the result can be negative when outdoor air is warmer than indoor, or any assumptions used.

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?

Two short, front-loaded sentences with no filler; the only mild redundancy is the German/English duplication, which is defensible for bilingual retrieval but does not add new information.

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?

The tool is simple (3 required numeric params, no enums, no nesting, no output schema), and the description covers the physical setup adequately. The notable gap is the missing result specification — with no output schema, an agent has no idea whether the returned number is in watts, kilowatts, or signed — which the description should have supplied.

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 each parameter already carries a unit, range, and meaning, so the description adds no parameter-level detail beyond what structured data provides. The baseline 3 applies since the schema does the heavy lifting.

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 (berechnen/estimate) and a specific physical quantity (fühlbare Wärmelast / sensible heat gain) with its source (nachströmende Außenluft bei einem Abluftgerät), so an agent can tell this is a calculation tool rather than a check or comparison tool. It does not explicitly contrast itself with any of the many klima_* siblings, which keeps it just short of a 5.

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 scenario is implied by 'bei einem Abluftgerät' (makeup air for an exhaust device), which tells an agent roughly when the tool applies. There is no statement of when not to use it, no prerequisites, and no named alternative for related tasks such as sizing or device selection, so guidance remains implicit.

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