Skip to main content
Glama

getecoback-raumklima

luftkuehler_modalternativen_lufttempo_partner

Read-only

Wählt aus zwei gemessenen Trockenstufen den geeigneteren Vergleichspartner für eine Nassprobe — Find the closest measured dry fan setting to an established wet-mode 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": "<nass>",
      "trocken_a": "<trocken_a>",
      "trocken_b": "<trocken_b>",
      "toleranz": "<toleranz>",
      "ort_gleich": "<ort_gleich>"
    },
    "name": "luftkuehler_modalternativen_lufttempo_partner"
  }
}

Input Schema

NameRequiredDescriptionDefault
nassYesTempo am Nutzplatz im Nassbetrieb in m/s.
toleranzYesEigene maximal zulässige Differenz in m/s.
trocken_aYesTempo bei der ersten erlaubten Trockenstufe in m/s.
trocken_bYesTempo bei der zweiten erlaubten Trockenstufe in m/s.
ort_gleichYesWurden alle Ablesungen am selben Messort auf gleichartige Weise erhoben?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety profile is covered by structured data. The description adds that selection is by 'closest' match, but says nothing about what happens when the tolerance is violated, how ort_gleich=false changes the outcome, or whether ties are possible. Some added value, but the decision rule stays opaque.

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 core operation front-loaded; nothing is padded. The German and English sentences are near-duplicates rather than complementary, which costs a little density but nothing is misleading.

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?

All five required parameters are documented and the tool is a read-only computation, so the essentials are present. However, with no output schema the description should indicate what is returned (which stage wins, a distance, or a failure when tolerance is exceeded) and how a false ort_gleich is handled; neither is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, and the description does map its wording onto the parameters: 'zwei gemessenen Trockenstufen' to trocken_a/trocken_b and 'Nassprobe' to nass, confirming the comparison direction. It adds no meaning for toleranz or ort_gleich beyond the schema, keeping it just above baseline rather than at the top.

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 concrete operation: pick, out of two measured dry fan stages, the better comparison partner for a wet sample, and adds the English gloss 'find the closest measured dry fan setting to an established wet-mode airflow'. That is a specific verb plus resource, and the 'two measured dry stages' scope separates it from broader airflow-measurement siblings, though it never names an alternative tool outright.

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?

Usage is only implied: the agent can infer this belongs to a wet-vs-dry comparison workflow with exactly two candidate dry readings. There is no explicit when-to-use statement, no guidance for the case where neither candidate is within tolerance, and no mention of which sibling handles the full wet/dry alignment (e.g. luftkuehler_nass_trocken_einlassabgleich).

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