Skip to main content
Glama

getecoback-raumklima

heissluft_schubladenpause_zonenzeit

Read-only

Tatsächliche Unterbrechung beider Zonen beim Öffnen einer Schublade protokollieren — Quantify observed zone downtime when a drawer is accessed.

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": {
      "vorgaenge": "<vorgaenge>",
      "pause_1_gesamt_s": "<pause_1_gesamt_s>",
      "pause_2_gesamt_s": "<pause_2_gesamt_s>",
      "gleiche_vorgaenge": "<gleiche_vorgaenge>"
    },
    "name": "heissluft_schubladenpause_zonenzeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorgaengeYesAnzahl vergleichbarer Entnahmevorgänge.
pause_1_gesamt_sYesBeobachtete Aussetzzeit von Zone 1 zusammen in Sekunden.
pause_2_gesamt_sYesBeobachtete Aussetzzeit von Zone 2 zusammen in Sekunden.
gleiche_vorgaengeYesBeide Summen beziehen sich auf dieselben Öffnungen und denselben Betriebszustand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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, and the description adds that only 'tatsächliche'/'observed' downtime counts, which is genuinely useful framing. However, 'protokollieren' suggests persisting a record while the annotations say read-only, and the description does nothing to resolve that tension or to say whether the counts are validated, averaged, or echoed back.

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 short line, front-loaded with the core concept before the English gloss. The bilingual restatement is mild padding and the duplicated framing slightly muddies the verb, but there is no filler beyond that.

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?

Four required parameters are well documented by the schema, but with no output schema the description should explain what the tool returns (per-zone downtime, per-event average, a comparison flag?) and it does not. For a quantification/analysis tool whose whole value is the derived result, that omission leaves the definition adequate but incomplete.

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%, including ranges (0-500 events, 0-86400 s) and the meaning of gleiche_vorgaenge, so the schema carries the parameter burden. The description only restates that both zones' interruption totals are involved ('beider Zonen'), adding essentially nothing beyond the structured fields — the baseline 3 applies.

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 identifies a subject (drawer-open downtime of both hot-air zones) and a verb ('protokollieren' / 'Quantify'), but the two halves point at different actions: logging an event versus computing a quantity. It never states what the call actually produces, so an agent knows the topic but not whether it records a measurement or returns a derived downtime figure.

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?

No when-to-use guidance is offered: no prerequisites (e.g. that measurements must already exist), no exclusions, and no routing to adjacent zone-related siblings such as heissluft_zonen_temperaturbedarf or heissluft_zwei_mengen_zonenwahl. The agent must infer the use case entirely from the domain vocabulary.

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