Skip to main content
Glama

getecoback-climate-weather

entfeuchter_bedienmatrix_ohne_app

Read-only

Für einen gemeinsam genutzten Entfeuchter prüfen, welche konkreten Schritte direkt am Gerät möglich sind — Map which household dehumidifier operations have a verified local control.

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": {
      "einstellen": "<einstellen>",
      "zustand_lesen": "<zustand_lesen>",
      "zeitplan_aendern": "<zeitplan_aendern>",
      "zeitplan_noetig": "<zeitplan_noetig>"
    },
    "name": "entfeuchter_bedienmatrix_ohne_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
einstellenYesLässt sich das gewünschte Ziel bzw. der gewählte Modus nachweislich vor Ort einstellen?
zustand_lesenYesIst der tatsächliche Zustand vor Ort eindeutig ablesbar?
zeitplan_noetigYesEine Änderung der Zeitfunktion gehört in dieser Situation tatsächlich zur Aufgabe?
zeitplan_aendernYesKann die für den Haushalt benötigte Zeitfunktion vor Ort geändert werden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 and the description does not contradict it ("verified local control" is consistent with a read-only assessment). What is missing is any disclosure of the evaluation behavior — e.g. how the four booleans are combined, whether the result is a pass/fail judgement, or what the agent receives back.

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 sentence is short and front-loaded, but it is stated twice — once in German and once in English — with the English half adding no new information beyond a literal restatement. Half the text is redundant duplication rather than additional specification.

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?

With four required parameters, no output schema, and no annotations covering results, the description should tell the agent what the call produces and how the booleans feed the outcome. It does neither, so the agent knows the topic but not the contract, which is a real gap for a decision-support tool.

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 each of the four booleans is already documented in the input schema; the baseline of 3 applies. The description adds no meaning beyond that — notably it does not explain that zeitplan_noetig acts as a gate for zeitplan_aendern, which is the one semantic relationship the schema leaves implicit.

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 verb-and-resource pair ("prüfen"/"map" which dehumidifier operations have verified local control) and scopes it to a shared device, but "welche konkreten Schritte direkt am Gerät möglich sind" stays abstract — it never names the four capability dimensions the schema actually evaluates. It is distinguishable from maintenance-oriented siblings (Ablaufcheck, Energie, Geruch), yet the agent cannot tell whether this tool reports a verdict, a checklist, or a plan.

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 only implicit context ("für einen gemeinsam genutzten Entfeuchter" / app-free operation) and no statement of when to call this versus the many other entfeuchter_* tools. No exclusions, no prerequisites, and no indication of what situation makes the boolean combination decision-relevant.

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