Skip to main content
Glama

getecoback-raumklima

luftbefeuchter_service_bedienanzeigen_abgleich

Read-only

Anzeige am Gerät mit Sollwert und aktivem Modus für die Herstellerfrage dokumentieren — Separate a missing setpoint display from a recorded manual mode.

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": {
      "modell": "<modell>",
      "anzeige": "<anzeige>",
      "modus_dokumentiert": "<modus_dokumentiert>",
      "lesbare_anleitung": "<lesbare_anleitung>"
    },
    "name": "luftbefeuchter_service_bedienanzeigen_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesExakte Modellfamilie in der vorhandenen Bedienungsanleitung.
anzeigeYesBeobachtete Anzeige.
lesbare_anleitungYesAnzeigeabschnitt für die eigene Variante griffbereit?
modus_dokumentiertYesBetriebsart in der eigenen Meldung mitnotiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safety is covered structurally, and the description is at least consistent with a pure recording operation. Beyond that it adds almost nothing: it does not say what the caller receives back, whether the record is persisted or merely formatted for the inquiry, or what happens if 'anzeige' is 'unleserlich'.

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?

It is short and front-loaded, but the German sentence and the English gloss largely restate each other in different words, which costs space without adding distinct information. The dual-language structure also reads as boilerplate rather than deliberate routing guidance.

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 parameters are fully described in the schema and the tool is a simple read-only capture, so the agent can call it. However, with no output schema and no statement about what the 'documentation' result looks like, the definition leaves a meaningful gap for a tool whose entire output is the documentation artefact.

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% and the two enum fields carry their own value lists, so the schema does the heavy lifting. The description only loosely maps onto parameters ('Sollwert' hints at zielwert_leuchtet, 'aktiver Modus' at modus_dokumentiert) and adds no format, ordering, or validation detail.

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 German clause names a verb and object ('Anzeige am Gerät mit Sollwert und aktivem Modus ... dokumentieren'), so the action is identifiable, but the pairing with a terse English gloss ('Separate a missing setpoint display from a recorded manual mode') makes the actual purpose ambiguous rather than crisp. No sibling tool is named, so an agent cannot tell from the description alone why this differs from e.g. luftbefeuchter_lokale_regelung_ersatzroutine or oskar_luftbefeuchter_zielstufe_dokumentiert.

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 'für die Herstellerfrage' implies the context of use — recording an observation to answer a manufacturer inquiry — but there is no explicit when-to-use, when-not-to-use, or alternative named. An agent must infer that this tool is for capturing display state rather than for diagnosing or fixing 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