Skip to main content
Glama

getecoback-climate-weather

luftkuehler_alternierende_nassphasen_sitzzeit

Read-only

Rechnet aus tatsächlichen Betriebsdauern nach, wie lange die Nassphase am Nutzplatz überhaupt genutzt wurde — Separate observed wet operation from the part actually used in the airflow.

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": {
      "nass_gesamt": "<nass_gesamt>",
      "davon_platz": "<davon_platz>",
      "weitere_lokale_min": "<weitere_lokale_min>"
    },
    "name": "luftkuehler_alternierende_nassphasen_sitzzeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
davon_platzYesIhr belegter Teil mit Nutzung am direkt angeströmten Platz in Minuten.
nass_gesamtYesBestätigte Gesamtdauer der Nassphasen in Minuten.
weitere_lokale_minYesGetrennte Nutzungsminuten an diesem Platz ohne Nassphase in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 it is a safe, closed-world computation; the description correctly stays consistent with that. It adds some context by framing the computation as a separation of observed total wet time from the portion actually exploited at the airflow point. It does not say whether the result can be negative, how the three minute values combine, or what the response contains, so the added value beyond annotations is modest.

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

Conciseness3/5

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

It is short, effectively one sentence plus a bilingual gloss, and the purpose is front-loaded. The second clause duplicates the first in another language instead of adding information, and the mid-sentence language switch makes it read as unpolished. Nothing is bloated, but the redundancy means not every part earns its place.

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?

This is a three-parameter computation with no output schema, so the description must carry the burden of explaining what comes back and how the inputs are combined — and it does not. An agent cannot tell whether the result is a number, a remainder, or a comparison, nor what to do with the separate dry-phase minutes. Given the tool's arithmetic nature, this leaves a meaningful gap.

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 each of the three minutes-valued parameters individually documented (total wet duration, the user's portion at the directly-flowed place, separate dry-phase minutes at that place), so the baseline is 3. The description adds a conceptual frame — observed operation versus actually used part — but no formula, unit handling, or constraint beyond the schema's 0–1440 bounds. It neither compensates nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a computation (back-calculating how long the wet phase was actually used at the seating point) from actual operating durations, which is a specific verb+resource. However, it mixes German and English mid-sentence and the English clause ('Separate observed wet operation from the part actually used in the airflow') restates the same idea rather than sharpening it, so the exact output — a duration, a ratio, a split — never becomes concrete. It does not distinguish itself from siblings such as the wet/dry or local-sample tools.

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?

There is no explicit statement of when to call this versus alternatives, and no prerequisites or exclusions. 'Rechnet aus tatsächlichen Betriebsdauern nach' implies the inputs must be observed durations, but that is inference, not guidance. No sibling is named, even though the catalog contains several closely related wet-phase and per-location 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