Skip to main content
Glama

getecoback-raumklima

kuehlgeraet_tueranzeige_protokollabgleich

Read-only

Vorhandene Türsignale mit selbst gemessenen Öffnungen abgleichen — Check whether observed door events correspond to the exact model’s alarm delay.

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": {
      "alarm_verzoegerung_s": "<alarm_verzoegerung_s>",
      "kuerzestes_signal_s": "<kuerzestes_signal_s>",
      "laengste_ohne_signal_s": "<laengste_ohne_signal_s>",
      "bedingungen_passend": "<bedingungen_passend>"
    },
    "name": "kuehlgeraet_tueranzeige_protokollabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedingungen_passendYesGleicher Modus, gleiche Tür und eindeutig dokumentiertes Signal in beiden Fällen.
kuerzestes_signal_sYesKürzeste protokollierte Öffnung mit Signal.
alarm_verzoegerung_sYesAuslöseverzögerung in Sekunden laut Anleitung für die gegebene Einstellung.
laengste_ohne_signal_sYesLängste protokollierte Öffnung ohne Signal.

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 the safety profile is covered by structured data. The description adds a meaningful constraint beyond that: the comparison must be against the exact model's documented alarm delay, implying model-matching matters. It does not disclose the return shape or what happens when 'bedingungen_passend' is false, which is the behaviour an agent most needs here.

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 compact sentence, front-loaded with the operation, with no padding or restated boilerplate. The German and English clauses are near-duplicates, which is mild redundancy but useful for disambiguation rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say what comes back, and it does in outline ('Check whether ... correspond' implies a verdict). Combined with a fully documented four-parameter schema and read-only annotations, an agent has enough to call it correctly; the main remaining gap is the treatment of the bedingungen_passend flag in the result.

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 all four parameters are already documented in the schema, and the baseline is 3. The description adds only light semantic framing ('self-measured openings', 'exact model's alarm delay') that maps loosely onto alarm_verzoegerung_s and the two signal-duration fields; it does not explain how the durations are compared against the delay.

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 ('abgleichen' / 'Check whether ... correspond') on a concrete resource (existing door signals vs. self-measured openings), and specifies that the comparison is against the exact model's alarm delay. That is specific enough to distinguish it from the neighbouring measurement and look-up tools. It stops short of 5 because it never states what a 'correspondence' verdict looks like, leaving the outcome of the check implicit.

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 guidance on when to invoke this tool rather than another, no prerequisites, and no exclusions. The phrase 'selbst gemessenen Öffnungen' implies you must already have measurements in hand, but this is inferred rather than stated. An agent gets no explicit trigger condition.

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