Skip to main content
Glama

getecoback-raumklima

delonghi_magnifica_entkalkungslampe_rot_blinkt_dauerlicht

Read-only

Ordnet die rote Entkalkungslampe der Magnifica S zwischen blinkender Aufforderung und laufendem Entkalkungsprogramm ein — Distinguish due and active descaling by the verified De’Longhi indicator.

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>",
      "symbol_bestaetigt": "<symbol_bestaetigt>",
      "signal": "<signal>"
    },
    "name": "delonghi_magnifica_entkalkungslampe_rot_blinkt_dauerlicht"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständige Modellkennung des deutschen Geräts.
signalYesBeobachtetes Licht.
symbol_bestaetigtYesIm genauen Bedienfeld ist die Kontrollleuchte der Entkalkung sicher identifiziert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 this is an interpretive classification rather than an action, and the word 'verified' implies the answer depends on confirmed identification of the lamp. It does not disclose what the tool produces (a verdict, a recommended next step, or a refusal), which is the main behavioral gap.

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 content is front-loaded and short, but the German and English sentences say the same thing, which is redundant padding rather than added information. The single-sentence structure is easy to scan, yet roughly half its length is duplicated content.

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 three parameters are fully documented and annotations cover the read-only nature, so an agent can call this correctly. What is missing is a statement of what comes back — the description never says whether the result is a classification label, an explanation, or a recommended action — and there is no output schema to fill that gap.

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 all three parameters including both enums are already documented in the schema, which sets the baseline at 3. The description reinforces the 'symbol_bestaetigt' concept via 'verified De'Longhi indicator' and frames the blink-vs-steady distinction that the 'signal' enum encodes, but adds no format or interpretation detail beyond that.

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 verb of interpretation ('Ordnet ... ein') applied to a specific resource (the red descaling lamp of the Magnifica S), and states the two states it separates: pending prompt versus running descaling program. This is far more than a restatement of the name. It stops short of a 5 because it does not explicitly contrast itself with any sibling tool, so an agent must infer that no other tool covers this lamp.

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?

Usage is only implied: the agent can deduce the tool applies when a red descaling lamp is observed on a Magnifica S. There is no explicit when-to-use or when-not-to-use statement, and no routing to an alternative (e.g., filter-change tools among the siblings) when the observed indicator turns out not to be the descaling lamp. The 'verified indicator' phrasing hints at a prerequisite but does not state one.

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