Skip to main content
Glama

getecoback-raumklima

ventilator_schwenkzyklus_luft_am_platz

Read-only

Ermittelt die beobachteten Luftstrom-Minuten an einem Platz bei Schwenkbetrieb — Estimate observed draft minutes at a seat using a measured oscillation cycle.

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": {
      "zyklus_sek": "<zyklus_sek>",
      "luft_am_platz_sek": "<luft_am_platz_sek>",
      "laufzeit_min": "<laufzeit_min>"
    },
    "name": "ventilator_schwenkzyklus_luft_am_platz"
  }
}

Input Schema

NameRequiredDescriptionDefault
zyklus_sekYesDauer einer vollständigen Schwenkperiode in Sekunden.
laufzeit_minYesNutzungsdauer mit derselben Einstellung in Minuten.
luft_am_platz_sekYesSekunden je Periode, in denen am Platz Luftstrom beobachtet wird.

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 and locality are covered. The description adds that the result is an *estimate* derived from a *measured* cycle, which is useful framing, but it does not state the returned unit explicitly (minutes vs. seconds) or the underlying relationship between inputs.

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 tight sentence pair with the resource and method front-loaded. The German/English duplication is mildly redundant but small, and no sentence is wasted.

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 pure computation with three fully documented parameters and no output schema, the description should say what comes back (unit and rough meaning) and ideally hint at the calculation. It implies minutes via 'Luftstrom-Minuten' but leaves the output contract and input relationship implicit, so it is adequate but not complete.

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 each of the three parameters bounded and described in German, so the schema carries the semantics. The description adds only the notion of a 'measured oscillation cycle' and does not clarify how the three values combine, which is the baseline 3 for a fully documented 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?

States a specific verb+resource in both languages: 'Ermittelt die beobachteten Luftstrom-Minuten an einem Platz bei Schwenkbetrieb' / 'Estimate observed draft minutes at a seat using a measured oscillation cycle.' An agent knows this computes draft exposure under oscillation. It stops short of naming or contrasting any sibling (e.g. ventilator_schwenkbereich_sitzplaetze), so it earns a 4 rather than a 5.

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 / when-not-to-use guidance and no named alternative among the many ventilator_* siblings. Usage must be inferred entirely from the purpose statement, which is a real gap in a crowded sibling namespace.

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