Skip to main content
Glama

getecoback-raumklima

ventilator_durchsatz_einheiten_stufenbezug

Read-only

Vereinheitliche Ventilator-Durchflusswerte und prüfe den Stufenbezug — Normalize fan airflow units and check operating speed context

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": {
      "wert_a": "<wert_a>",
      "wert_b": "<wert_b>",
      "einheit_a": "<einheit_a>",
      "einheit_b": "<einheit_b>",
      "gleicher_stufenbezug": "<gleicher_stufenbezug>"
    },
    "name": "ventilator_durchsatz_einheiten_stufenbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
wert_aYesLuftdurchsatz von Gerät A
wert_bYesLuftdurchsatz von Gerät B
einheit_aYesEinheit A
einheit_bYesEinheit B
gleicher_stufenbezugYesBeide Werte haben den gleichen dokumentierten Stufenbezug

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed computation. The description adds nothing about the outcome, such as which unit is the target of normalization or what happens when gleicher_stufenbezug is false, and there is no output schema to fill that gap.

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?

A single front-loaded sentence that pairs the German and English phrasing without padding. Nothing extraneous, and the two operations are ordered clearly.

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 five-required-parameter computation tool with no output schema, so the description should explain the result shape (e.g., which value is converted to which unit, what the boolean check yields). It does not, leaving the tool's actual return behavior entirely undefined.

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 every one of the five required parameters documented in the schema itself, so the description is not required to carry parameter meaning. The description only echoes the concepts 'Einheiten' and 'Stufenbezug' without adding direction, defaults, or interpretation rules 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 two specific operations on a specific resource: normalizing fan airflow units ('Vereinheitliche Ventilator-Durchflusswerte') and checking the speed-stage reference. This is concrete enough to distinguish it from the scenario-oriented siblings, though it stops short of explaining what the normalization results in.

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 description implies when the tool is relevant (comparing two devices' airflow), but it never states when to use it instead of another tool, nor any exclusions or prerequisites such as requiring compatible documented stage references. Usage must be inferred from the name and parameters.

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