Skip to main content
Glama

getecoback-raumklima

induktion_stop_go_laufende_timer_pausenannahme

Read-only

Prüfe anhand des beobachteten Stop&Go-Intervalls, wie viel einer vorher belegten Timerzeit ohne Eingriff abläuft — Compare a recorded Stop&Go interval to the running timer

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>",
      "stoppmodus_dokumentiert": "<stoppmodus_dokumentiert>",
      "bekannter_timer": "<bekannter_timer>",
      "rest_beim_beginn_s": "<rest_beim_beginn_s>",
      "stop_go_dauer_s": "<stop_go_dauer_s>",
      "ununterbrochene_zuordnung": "<ununterbrochene_zuordnung>"
    },
    "name": "induktion_stop_go_laufende_timer_pausenannahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
bekannter_timerYesVorher nachweislich laufende Zeit
stop_go_dauer_sYesTatsächlich beobachtete Sekunden im ausgewerteten Stop&Go-Intervall
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt
rest_beim_beginn_sYesDokumentierte verbleibende Sekunden dieses Timers zum Beginn von Stop&Go
stoppmodus_dokumentiertYesStop&Go war für dieses Intervall tatsächlich angezeigt
ununterbrochene_zuordnungYesSelber Lauf und Timer, ohne unaufgeklärte Unterbrechung oder früher erkanntes Ende

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 the comparison semantics (compute elapsed timer time without intervention) but does not say what the result looks like or what happens when the mandatory gate booleans (modell_bestaetigt, stoppmodus_dokumentiert, ununterbrochene_zuordnung) are false — precisely the behavior an agent needs to anticipate.

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?

Two short clauses with the action front-loaded; nothing is padded. The German and English halves convey identical information, a minor redundancy that aids disambiguation for mixed-language agents rather than adding noise.

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 computation with six required parameters and no output schema, the description should at least characterize the returned quantity and the effect of unmet preconditions. It conveys the conceptual comparison but leaves the result and failure behavior undocumented, which is a meaningful gap even with full schema coverage.

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 parameters including the enum and bounded numeric ranges are fully documented in the schema. The description adds only a light conceptual frame ("vorher belegte Timerzeit", "beobachtetes Stop&Go-Intervall") without clarifying units, bounds, or how the gate flags interact, so the baseline 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?

"Prüfe ... wie viel einer vorher belegten Timerzeit ohne Eingriff abläuft" states a specific operation (compare a recorded Stop&Go interval against a running timer) with a clear input premise. The bilingual restatement reinforces meaning, but the description never names or contrasts any of the many sibling timer tools, so differentiation is left to the name alone.

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 tool applies when a Stop&Go interval has been observed and a timer time was previously documented. There is no explicit when-not guidance and no pointer to an alternative tool, but the precondition it states is specific enough for an agent to infer the right context.

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