Skip to main content
Glama

getecoback-climate-weather

induktion_booster_laufzeit_und_beobachtete_phase

Read-only

Ordne das beobachtete Booster-Ende und eine Leistungsprobe dem passenden Abschnitt zu — Distinguish an observed booster interval from subsequent operation

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_bestaetigt": "<start_bestaetigt>",
      "ende_beobachtet": "<ende_beobachtet>",
      "ende_ab_start_min": "<ende_ab_start_min>",
      "probe_start_min": "<probe_start_min>",
      "probe_ende_min": "<probe_ende_min>"
    },
    "name": "induktion_booster_laufzeit_und_beobachtete_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
probe_ende_minYesEnde des ausgewerteten Intervalls, relativ zur Aktivierung
ende_beobachtetYesEnde des Boosterstatus ausdrücklich beobachtet
probe_start_minYesBeginn des ausgewerteten Intervalls, relativ zur Aktivierung
start_bestaetigtYesAktivierung auf genau derselben Zone mit Zeitstempel dokumentiert
ende_ab_start_minYesBeobachtetes Ende ab Aktivierung, bei fehlender Ende-Beobachtung ignoriert
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt

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 state that the tool is read-only and closed-world, so the safety profile is covered. The description adds the idea of distinguishing an observed booster interval from subsequent operation, but it does not explain how the assignment is decided or what the resulting section means.

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 description is short and front-loaded, but the bilingual construction is awkward and leaves key terms such as 'Abschnitt' and 'Leistungsprobe' ambiguous. It is concise without being sufficiently clear.

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?

This is a six-parameter classification tool with no output schema, so the description needs to explain the mapping logic and expected interpretation. Instead it provides only a brief framing sentence and no detail about how the assignment should be understood.

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 six required parameters are already documented in the input schema. The description adds only a high-level framing and no additional meaning about how the parameters interact or how the intervals are evaluated.

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 names a specific action ('Ordne ... zu') and resources (observed booster end, power test, matching section), but 'passenden Abschnitt' remains undefined. The added English clause clarifies the distinction being made, yet the overall purpose is still only partially clear.

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?

It gives no explicit guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. The agent must infer usage entirely from the name and parameter set.

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