Skip to main content
Glama

getecoback-raumklima

luftkuehler_mattemuster_nasszonen_nachlauf

Read-only

Trennt wiederholt trockene Mattenfelder von nur einmal beobachteten trockenen Feldern — Distinguish repeatedly dry pad areas from one-off readings after use.

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": {
      "felder": "<felder>",
      "trocken_a": "<trocken_a>",
      "trocken_b": "<trocken_b>",
      "dieselben": "<dieselben>",
      "gleiche_nachlaufzeit": "<gleiche_nachlaufzeit>"
    },
    "name": "luftkuehler_mattemuster_nasszonen_nachlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
felderYesAnzahl gleicher, auf vorhandenen Bildern sichtbarer Felder.
dieselbenYesIn beiden Bildern dieselben trockenen Felder.
trocken_aYesTrockene Felder nach erstem Lauf.
trocken_bYesTrockene Felder nach zweitem Lauf.
gleiche_nachlaufzeitYesGleiche Sichtseite und gleich lange Zeit bis zur vorhandenen Sichtbeobachtung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 is covered. Beyond that the description discloses nothing: it does not say what happens when 'dieselben' exceeds 'trocken_a'/'trocken_b', whether 'gleiche_nachlaufzeit' gates the result or invalidates it, or how the two-reading comparison behaves under unequal conditions.

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 first. The German/English duplication is somewhat redundant but short enough and aids comprehension; nothing extraneous beyond that translation pair.

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?

With five required numeric/boolean inputs and no output schema, the description carries full responsibility for explaining the returned result, and it does not — an agent cannot tell whether it receives booleans, field lists, or aggregate counts. For a non-trivial set comparison the definition is under-specified.

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 every parameter including 'gleiche_nachlaufzeit' is documented in the schema; the description adds no parameter-level meaning beyond it. That meets the baseline for a fully-described schema but earns nothing extra.

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 specific operation ('Trennt ... trockene Mattenfelder von nur einmal beobachteten trockenen Feldern'), so the verb and the compared categories are visible. However, it never states what the separation produces (a classification, counts, ratios?) and gives no cue distinguishing it from closely-named siblings such as luftkuehler_nass_trocken_einlassabgleich or luftkuehler_pflegedokument_tank_matte_unterscheiden.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool for the same comparison. The 'nach Benutzung' phrase hints at a post-use context but does not define when this analysis is required versus the neighboring luftkuehler_* comparison 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