Skip to main content
Glama

getecoback-climate-weather

kuehlschrank_tuerroutine_ereignisse_sammelphase

Read-only

Bei länger erfassten Kühlschrankläufen eindeutig einzelne Zugriffsfenster von untrennbaren Gruppen unterscheiden — Decide which logged door periods can serve as isolated observations.

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": {
      "einzeln_vorgemerkt": "<einzeln_vorgemerkt>",
      "weitere_oeffnung_darin": "<weitere_oeffnung_darin>",
      "davon_erneut_ganz_geloggt": "<davon_erneut_ganz_geloggt>",
      "nachbeobachtung_gleich": "<nachbeobachtung_gleich>"
    },
    "name": "kuehlschrank_tuerroutine_ereignisse_sammelphase"
  }
}

Input Schema

NameRequiredDescriptionDefault
einzeln_vorgemerktYesUrsprünglich als isolierte Zugriffsfenster vorgemerkte Phasen.
nachbeobachtung_gleichYesFür alle Fenster war dieselbe nachbeobachtete Dauer eindeutig erfasst.
weitere_oeffnung_darinYesDavon Phasen mit einer weiteren Öffnung vor Ende des nachbeobachteten Abschnitts.
davon_erneut_ganz_geloggtYesSeparat neu beobachtete und vollständig protokollierte Einzelfenster für die ursprünglich überlagerten Phasen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and there is no contradiction. Beyond that the description adds almost no behavioral detail: it does not say whether the outcome is a yes/no classification per window, an aggregate count, or how ties/ambiguity are handled.

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 short and front-loaded, leading with the qualifying condition and then the decision to be made. The German sentence and its English rendering say the same thing, which is slightly redundant but not harmful.

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?

For a four-required-parameter decision tool with no output schema, the description leaves the crucial part underspecified: what the tool actually produces (a filtered set, a boolean per window, counts). An agent can supply the inputs but cannot predict the result, which is a real gap given the complexity of the domain.

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 four parameters (einzeln_vorgemerkt, weitere_oeffnung_darin, davon_erneut_ganz_geloggt, nachbeobachtung_gleich) are already explained in the schema. The description adds no meaning to these inputs, which is acceptable given full coverage but earns only the baseline.

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 an operation ('unterscheiden'/'decide') on a resource ('einzelne Zugriffsfenster' vs. 'untrennbare Gruppen' of logged door periods), so the intent is broadly graspable. But it is stated in abstract, jargon-heavy terms and gives no hint of how it differs from siblings such as kuehlschrank_tueroeffnung_alltag or the other kuehlschrank_* tools, so an agent cannot route confidently from purpose 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?

'Bei länger erfassten Kühlschrankläufen' supplies a qualifying context for when the tool applies, which is more than nothing. There is no explicit when-not condition, no mention of prerequisites, and no named alternative for shorter or simpler runs.

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