Skip to main content
Glama

getecoback-raumklima

entfeuchter_abtauzeit_im_protokoll

Read-only

Laufzeit mit belegter Abtauanzeige getrennt von unbekannten Unterbrechungen erfassen — Separate logged defrost time from unexplained periods in a service report.

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": {
      "protokoll_min": "<protokoll_min>",
      "abtauanzeige_min": "<abtauanzeige_min>",
      "unklar_min": "<unklar_min>",
      "anzeige_belegt": "<anzeige_belegt>"
    },
    "name": "entfeuchter_abtauzeit_im_protokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
unklar_minYesZusätzliche Minuten ohne belastbar bekannten Betriebszustand.
protokoll_minYesLänge des vorhandenen Protokolls in Minuten.
anzeige_belegtYesZuordnung der Anzeige zum Abtauen in der Modellanleitung bestätigt?
abtauanzeige_minYesZeit mit für dieses Modell bestätigter Abtauanzeige.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The read-only and closed-world annotations already establish the safety profile. The description adds that the tool separates confirmed defrost time from unexplained interruptions, but it does not explain the result format, calculation behavior, or how the separation is represented.

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?

The description is compact and front-loads the action and resource. The German sentence is repeated in English, which is useful for clarity but slightly redundant.

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?

The input schema is fully described and the annotations cover safety, but there is no output schema and the description does not state what result the tool returns. It is adequate for invoking the tool, but leaves an important gap around returned values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each parameter. The description adds a useful relational meaning by framing abtauanzeige_min as the logged defrost time to be separated from the unexplained periods represented by unklar_min.

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 gives a specific verb and resource: it separates logged defrost time from unexplained periods in a service report. The purpose is clear, but no sibling tool is named or explicitly differentiated, so it falls short of the top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'in a service report' implies the context in which the tool is used, but the description does not state when to choose this tool over alternatives or when not to use it. Usage is therefore only implicitly conveyed.

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