Skip to main content
Glama

getecoback-raumklima

entfeuchter_tankmeldung_uebergabe

Read-only

Einen getesteten Empfangsweg für die Tankmeldung festlegen — Assign a checked human handoff when the dehumidifier tank indication is hard to notice.

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": {
      "ton_bemerkt": "<ton_bemerkt>",
      "sichtmeldung_bemerkt": "<sichtmeldung_bemerkt>",
      "app_meldung_bemerkt": "<app_meldung_bemerkt>",
      "kontrollabstand_min": "<kontrollabstand_min>"
    },
    "name": "entfeuchter_tankmeldung_uebergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
ton_bemerktYesWar der vorgesehene Ton am üblichen Aufenthaltsort im normalen Zustand tatsächlich zu hören?
app_meldung_bemerktYesWurde eine passende Modellmeldung ohne Betreten des Raums im vorgesehenen Test tatsächlich empfangen?
kontrollabstand_minYesGeplanter Abstand für bewusstes Nachsehen am Gerät, 0 falls noch nicht eingeplant.
sichtmeldung_bemerktYesWurde die Anzeige am üblichen Kontrollort tatsächlich gesehen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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. The description adds that the handoff must be 'getestet/checked' — i.e. grounded in prior test observations — which is useful context. However, it does not explain what the tool actually returns (a recommendation? a persisted plan?) and 'festlegen' could be misread as a write operation despite the readOnly hint.

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 bilingual sentence with no filler, and the purpose is front-loaded before the conditional clause. The German half is dense and the English rendering is loose, but nothing is 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?

All four required inputs are well covered by the schema, so an agent can call the tool correctly. Because there is no output schema, the description should say what the 'handoff' result looks like (e.g. a recommended alert channel plus follow-up interval) and does not, leaving the return value a blind spot.

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%, with each of the four required fields (three observation booleans and a control interval in minutes) fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 specific action ('einen getesteten Empfangsweg ... festlegen' / 'Assign a checked human handoff') tied to a specific trigger (dehumidifier tank indication). The combination of verb and resource lets an agent distinguish it from siblings like entfeuchter_tank_leerintervall, though the abstract term 'Empfangsweg'/'handoff' makes the concrete output slightly hard to picture.

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?

A use condition is given implicitly via the trigger phrase 'when the dehumidifier tank indication is hard to notice', which tells an agent the problem situation. There is no explicit statement of when NOT to use it and no named alternative for the case where the indication is easily noticed.

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