Skip to main content
Glama

getecoback-climate-weather

luftreiniger_cadr_luefterstrom_kennzeichnung

Read-only

Berechne die Reinluftmenge eines Betriebsabschnitts nur aus ausgewiesener Partikel-CADR — Calculate clean-air volume only from a documented particle CADR

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": {
      "angabe_m3_h": "<angabe_m3_h>",
      "kennzeichnung": "<kennzeichnung>",
      "bezug": "<bezug>",
      "abschnitt_min": "<abschnitt_min>"
    },
    "name": "luftreiniger_cadr_luefterstrom_kennzeichnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
bezugYesBezieht sich der Wert auf die tatsächlich eingesetzte Gerätestufe?
angabe_m3_hYesAufgedruckter Volumenstrom in m³/h
abschnitt_minYesMinuten bei der betrachteten Stufe
kennzeichnungYesWie bezeichnet die Unterlage den Wert?

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 safety is covered and the bar is lower. The description adds the substantive constraint that only documented particle CADR is accepted, but it never states what happens when kennzeichnung is "luefter_durchsatz" or "offen" — error, zero, or a warning — which is the main behavioral question for this tool.

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 sentences with the key constraint front-loaded; nothing is padded. The bilingual restatement is duplicative but conventional in this toolset and does not obscure the core statement.

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 four required parameters, two of them enums, and no output schema, the definition should clarify what quantity is returned and how non-CADR labels are handled. It identifies the computed quantity but leaves the non-CADR outcome and the return unit unstated, which is a meaningful gap for a tool whose whole premise is a label check.

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%, including enum documentation for kennzeichnung and bezug, so the schema does the heavy lifting and baseline 3 applies. The description reinforces the kennzeichnung=partikel_cadr requirement and ties the calculation to an operating section, but adds no syntax, unit, or edge-case detail 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 names a specific verb and output ("Berechne die Reinluftmenge" / "Calculate clean-air volume") scoped to one Betriebsabschnitt, and adds a real restriction ("nur aus ausgewiesener Partikel-CADR"). It distinguishes itself from CADR-related siblings only implicitly via that restriction, never naming an alternative tool.

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 "only from a documented particle CADR" functions as a when-to-use condition, telling the agent this tool applies when the datasheet labels the value as particle CADR. However, no alternative is named for the case where the label is a fan throughput ("luefter_durchsatz"), and the enum allows exactly that value, so the agent is left to infer what to do.

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