Skip to main content
Glama

getecoback-raumklima

entfeuchter_raumprotokoll_ablaufzweige

Read-only

Halte ungezählten Direktablauf von messbaren Tank- und Sammelmengen getrennt — Track counted and unmetered dehumidifier drainage after a transfer

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": {
      "tank_l": "<tank_l>",
      "sammelbehaelter_l": "<sammelbehaelter_l>",
      "direktablauf_min": "<direktablauf_min>",
      "raumphase_min": "<raumphase_min>",
      "alle_wege_erfasst": "<alle_wege_erfasst>"
    },
    "name": "entfeuchter_raumprotokoll_ablaufzweige"
  }
}

Input Schema

NameRequiredDescriptionDefault
tank_lYesIm Tank für diesen Raum erfasste Liter, 0 wenn keine erfasst
raumphase_minYesGesamtdauer der dokumentierten Raumphase
direktablauf_minYesProtokollierte Minuten mit ungezähltem Direktablauf
alle_wege_erfasstYesAuch Leerungen, Überlauf und Moduswechsel sind im Protokoll abgedeckt
sammelbehaelter_lYesSeparat im Sammelgefäß erfasste Liter, ohne Doppelzählung

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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. The description adds only a semantic separation rule ('ohne Doppelzählung' is in the schema, not the description) and says nothing about what happens when alle_wege_erfasst is false, whether the call validates or rejects inconsistent input, or what is returned — notable since no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loads the core concept, but it is a bilingual restatement — the German clause and the English clause convey the same content, so half the text is redundant rather than additive. No wasted length, but no added information either.

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

Completeness2/5

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

Five required parameters, no output schema, and an ambiguous operation make this a case where the description must carry more weight. It never states what the result represents (a remainder, a balance, a validation verdict) or how the required alle_wege_erfasst flag changes the outcome, leaving the agent unable to predict or interpret the call.

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% with per-field descriptions, so the baseline is 3. The description does contribute the framing that counted quantities (tank_l, sammelbehaelter_l) must be kept distinct from unmetered minutes (direktablauf_min), which helps an agent interpret why both kinds of parameters coexist, but it adds no units, boundaries, or interaction rules beyond the schema.

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 specific domain concept — separating unmetered direct drainage (direktablauf_min) from counted tank and collector volumes in a room protocol — but the operative verb ('Halte ... getrennt' / 'Track') never says what the tool actually does with these numbers: record, validate, compute a balance, or flag a gap. It is distinguishable from generic tank tools, but an agent cannot tell what output to expect from the call.

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?

The trailing phrase 'after a transfer' implies a prerequisite condition, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative among the many sibling entfeuchter protocol tools. Nothing tells the agent which of the ~30 sibling tools this one supersedes or complements.

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