Skip to main content
Glama

getecoback-raumklima

delonghi_magnifica_kaffee_pause_wiedergebrauch_spuelen

Read-only

Prüft vor dem ersten Kaffee nach mehrtägigem Nichtgebrauch die dokumentierte Spülempfehlung der De’Longhi Magnifica S — Read the rinse guidance for resuming use after a documented idle period.

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>",
      "ruhe_dauer_belegt": "<ruhe_dauer_belegt>",
      "tage": "<tage>",
      "spuelung_vor_nutzung": "<spuelung_vor_nutzung>"
    },
    "name": "delonghi_magnifica_kaffee_pause_wiedergebrauch_spuelen"
  }
}

Input Schema

NameRequiredDescriptionDefault
tageYesDauer des Nichtgebrauchs in Tagen, anteilige Tage sind erlaubt.
modellYesGenaue Modellkennung in Deutschland.
ruhe_dauer_belegtYesUnunterbrochener Zeitraum ohne Betrieb ist für das Exemplar dokumentiert.
spuelung_vor_nutzungYesErfolgte Reinigung oder Spülung nach Wiederbeginn ist als eigener Vorgang belegt.

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 one meaningful behavioral fact, that it consults documented guidance rather than executing a rinse, but does not say what the outcome looks like or how the four evidence fields are weighed.

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?

Short and front-loaded, with the trigger condition stated first. The English half is a near-verbatim restatement of the German and earns little beyond the original, though the bloat is limited to one clause.

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?

For a read-only lookup with no output schema and a fully described schema, the definition is close to adequate. The gap is that it never explains how the four required evidence fields combine or what a negative determination means, which matters because every parameter is mandatory.

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 the four parameters and both enums are already fully documented in the schema. The description only echoes the idle-period concept ('mehrtägigem Nichtgebrauch'), adding no interpretation of ruhe_dauer_belegt or spuelung_vor_nutzung. Baseline 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?

States a specific verb plus resource ('Prüft ... die dokumentierte Spülempfehlung') and pins the device ('De'Longhi Magnifica S'), so the agent knows this is a guidance lookup tied to one model. It does not differentiate itself from sibling diagnostic tools by name, but the scope is concrete enough to act on.

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?

Gives a trigger condition ('vor dem ersten Kaffee nach mehrtägigem Nichtgebrauch'), which implies when to call. It offers no exclusions, no prerequisites about documenting the idle period, and no alternative tool for the cases where the idle period is undocumented or the model is different.

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