Skip to main content
Glama

getecoback-climate-weather

ventilator_mittelstufe_aus_gegenrichtungen_beobachten

Read-only

Vergleicht dieselbe Lüfterstufe nach beobachtetem Hoch- und Herunterschalten — Compare sound on one fan setting reached from two directions.

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": {
      "von_unten_db": "<von_unten_db>",
      "von_oben_db": "<von_oben_db>",
      "gleiche_setzzeit": "<gleiche_setzzeit>",
      "laute_reihenfolge_abweichung_db": "<laute_reihenfolge_abweichung_db>"
    },
    "name": "ventilator_mittelstufe_aus_gegenrichtungen_beobachten"
  }
}

Input Schema

NameRequiredDescriptionDefault
von_oben_dbYesA-gewichteter Messwert auf derselben Zielstufe nach regulärem Herunterschalten in dB.
von_unten_dbYesA-gewichteter Messwert auf der Zielstufe nach regulärem Hochschalten in dB.
gleiche_setzzeitYesGleiche Wartezeit, Mittelungsdauer, Oszillation und Messposition?
laute_reihenfolge_abweichung_dbYesSelbst gesetzter Differenzwert für eine erneute Beobachtung in dB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that the description mostly restates the tool name, adding only that the quantity compared is sound; it says nothing about what a discrepancy implies, what happens if gleiche_setzzeit is false, or how results should be interpreted.

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, front-loaded with the core operation, with no filler. The German/English duplication is slightly redundant but aids disambiguation rather than obscuring it.

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?

For a read-only four-parameter observation tool with fully documented schema and no output schema required, the definition is minimally adequate. It still leaves the interpretation of laute_reihenfolge_abweichung_db and the meaning of an observed direction difference unexplained.

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% and each of the four required parameters carries its own unit and range documentation, so the schema does the heavy lifting. The description adds no syntax, measurement-protocol, or threshold semantics beyond what those field descriptions already say.

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 (comparing measured sound on the same fan level reached via up-shift vs down-shift), which is more specific than the name alone and lets an agent identify the hysteresis-check concept. It does not, however, contrast itself with nearby siblings such as ventilator_stufenwahl_tastendruecke or ventilator_uebergabe_markierte_stufenpaare.

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, when-not-to-use, or alternative-tool guidance. The agent must infer that this is the tool for detecting direction-dependent level differences, and nothing tells it what to do instead when the two directions are irrelevant.

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