Skip to main content
Glama

getecoback-raumklima

monoblock_kuehlmodus_einstellung_pruefen

Read-only

Fehlende Kühlung zunächst anhand von Betriebsart, Sollwert und aktivem Timer einordnen — Troubleshoot obvious control settings before treating a running portable AC as defective.

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": {
      "modus": "<modus>",
      "raum_c": "<raum_c>",
      "soll_c": "<soll_c>",
      "einschaltverzoegerung": "<einschaltverzoegerung>"
    },
    "name": "monoblock_kuehlmodus_einstellung_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
modusYesAktuell angezeigte Betriebsart.
raum_cYesRaumtemperatur am Aufstellort.
soll_cYesDerzeit eingestellter Zielwert.
einschaltverzoegerungYesDas Gerät zeigt einen Timer oder eine laut Anleitung laufende Einschaltverzögerung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The readOnly and closed-world annotations already establish that this is a safe inspection tool. The description adds useful triage context, but it does not explain what kind of assessment or output the agent should expect from 'einordnen'.

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 definition is short and front-loads the diagnostic purpose. The German sentence and English follow-up overlap somewhat, but the English sentence adds the useful 'running portable AC as defective' framing.

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?

All four parameters are required and fully described in the schema, and the description supplies the diagnostic framing. However, with no output schema, it should clarify what result or classification the agent will get back.

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 coverage is 100%, so the parameters are already fully documented. The description references operating mode, setpoint, and timer, but omits room temperature and adds no syntax or interpretation beyond the 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?

The description states a specific diagnostic action: classifying missing cooling based on operating mode, setpoint, and an active timer. It is clearly a pre-diagnosis check rather than a repair action, though it does not explicitly distinguish itself from similar sibling check tools.

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

Usage Guidelines4/5

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

The word 'zunächst' and the phrase 'before treating a running portable AC as defective' give clear sequencing guidance: use this first for obvious control-setting issues. It does not name explicit alternative tools or when not to use it.

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