Skip to main content
Glama

getecoback-climate-weather

induktion_vorfuehrgeraet_demomodus_heizbeleg

Read-only

Prüfe bei einem Vorführ- oder Gebrauchtgerät, ob eine Aufzeichnung nur den dokumentierten Demomodus oder auch eine beobachtete Heizfunktion belegt — Check second-hand or showroom heating evidence against demo 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_bestaetigt": "<modell_bestaetigt>",
      "start_timersignal": "<start_timersignal>",
      "heizbeobachtung": "<heizbeobachtung>",
      "gleicher_lauf_und_geraet": "<gleicher_lauf_und_geraet>"
    },
    "name": "induktion_vorfuehrgeraet_demomodus_heizbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
heizbeobachtungYesBereits protokollierte Heizbeobachtung, keine neue Prüfung auslösen
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt
start_timersignalYesBeim Start auf genau diesem Gerät aufgezeichneter Timertext
gleicher_lauf_und_geraetYesAnzeige und beobachtete Funktion sind demselben Gerät und Start eindeutig zugeordnet

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?

The readOnlyHint=true and openWorldHint=false annotations already establish a safe, closed-world check, and 'Prüfe' is consistent with that. The description adds the evidentiary comparison being made, but does not explain result shape, interpretation, rate limits, or other behavioral detail beyond annotations.

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?

The definition is a single front-loaded sentence with no filler and puts the check before the translation. The German/English duplication is slightly redundant but not materially wasteful.

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 four-required-parameter evidentiary check with enums and no output schema, the description gives the core purpose but omits how the result is classified or returned. It is adequate for invocation but leaves meaningful interpretive gaps.

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 input schema already documents all four required parameters and their enums. The description echoes the high-level concepts of demo mode and observed heating but adds no new per-parameter meaning, edge cases, or validation semantics beyond the schema.

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 ('Prüfe') and a precise decision object: whether a recording proves only documented demo mode or also an observed heating function for a showroom/used device. It is clear enough to separate from general induction tools, though it does not name alternatives.

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 description supplies the scenario ('Vorführ- oder Gebrauchtgerät'), which implies when the tool is relevant, but it gives no explicit when-to-use versus when-not-use guidance, prerequisites, or named sibling alternatives.

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