Skip to main content
Glama

getecoback-climate-weather

luftreiniger_stufenplan_reinluftmenge

Read-only

Berechnet die restliche Laufzeit auf einer leiseren Stufe für eine vorgegebene Reinluftmenge — Calculate remaining quiet-stage time toward a specified clean-air volume.

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": {
      "ziel_m3": "<ziel_m3>",
      "erste_stufe_m3h": "<erste_stufe_m3h>",
      "erste_min": "<erste_min>",
      "zweite_stufe_m3h": "<zweite_stufe_m3h>"
    },
    "name": "luftreiniger_stufenplan_reinluftmenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_m3YesGewünschtes rechnerisches Reinluftvolumen in m³.
erste_minYesLaufzeit der ersten Stufe in Minuten.
erste_stufe_m3hYesPartikel-CADR der ersten Stufe in m³/h.
zweite_stufe_m3hYesPartikel-CADR der zweiten Stufe in m³/h.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered by structured data. Beyond restating that this is a computation, the description discloses nothing about the calculation model — no assumption that volume already delivered equals erste_min × erste_stufe_m3h, no note on unit of the output (minutes), no treatment of edge cases such as a target already met. Nothing here is contradictory, but little is added.

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?

A single front-loaded sentence with the core operation stated first. The German and English halves are exact duplicates, which costs a little space, but the whole thing is short and unambiguous.

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?

With no output schema, the description should say what the returned value represents and on which basis the arithmetic works; it says neither, so an agent knows the purpose but not the result's unit or formula. For a simple four-parameter calculator with fully documented inputs, this is adequate but leaves a real 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%, so all four parameters (target volume, first-stage runtime, first- and second-stage CADR) are already documented with units and bounds. The description only gestures at two of them ('vorgegebene Reinluftmenge', 'leisere Stufe') and adds no syntax or semantic detail beyond the schema, which is the expected baseline 3.

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 and resource: it calculates the remaining runtime on a quieter stage to reach a given clean-air volume, and does so in both German and English. An agent can identify the operation without opening the schema, though nothing in the text distinguishes it from near neighbours like the two-stage outside-air comparison or the CADR duty-cycle balance tool.

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 when-to-use, when-not-to-use, or pointer to an alternative tool. The condition that selects this tool (a prior stage already ran and you want remaining time at a lower stage) must be inferred from the parameter names rather than read from the description.

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