Skip to main content
Glama

getecoback-raumklima

luftkuehler_feuchtemessung_nahstrahl_raumvertretung

Read-only

Trennt Feuchtewerte aus direktem Austrittsstrom von einem gleichzeitig erfassten Raumpunkt — Classify a humidity reading by its documented exposure to the cooler’s jet.

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": {
      "sichtwert": "<sichtwert>",
      "zweiter_wert": "<zweiter_wert>",
      "erster_standort": "<erster_standort>",
      "zweiter_raum_belegt": "<zweiter_raum_belegt>"
    },
    "name": "luftkuehler_feuchtemessung_nahstrahl_raumvertretung"
  }
}

Input Schema

NameRequiredDescriptionDefault
sichtwertYesAngezeigte relative Feuchte am ersten Punkt in % relativer Feuchte.
zweiter_wertYesAngezeigte Feuchte an einem zweiten Punkt in % relativer Feuchte.
erster_standortYesLage der ersten Messung.
zweiter_raum_belegtYesZweiter Sensor außerhalb direkter Anströmung an einem dokumentierten Raumpunkt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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. The description adds the substantive behavioral point that the classification is based on documented exposure (jet vs room point), but says nothing about permissions, edge cases, or what happens when exposure is 'unklar'.

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 clauses with the German statement followed by an English gloss; nothing is redundant. Front-loading is good, though the abstract wording ('documented exposure') costs a little clarity.

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 four required parameters are documented in the schema and annotations cover safety, but with no output schema the description never states what the classification result looks like – the central payload of a classification tool – leaving a real gap for a 4-parameter tool.

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 the baseline is 3. The description only alludes loosely to the parameters by mentioning the jet and a room point, without adding format, units, or the meaning of 'unklar' or the boolean 'zweiter_raum_belegt' beyond what the schema already states in German.

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 concrete operation – separating/classifying humidity values from the direct outlet stream versus a simultaneously recorded room point – so the agent knows this is a classification-of-measurement-context tool. It is clear about the verb and resource but never contrasts itself with the many other luftkuehler_* tools that also handle humidity readings.

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 statement, no prerequisites, and no named alternative among a large sibling set. The condition is only implied by the phrase 'documented exposure to the cooler's jet', which the agent must infer selects this tool over e.g. the outlet-measurement or wet/dry-abgleich siblings.

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