Skip to main content
Glama

getecoback-raumklima

klimageraet_verlauf_ausfallphasen_ungeklaert

Read-only

Bilanziere während einer Kühlprobe aktive, geplante und ungeklärte Ausfallzeit getrennt — Separate active cooling, planned pauses and unresolved downtime

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": {
      "probe_min": "<probe_min>",
      "kuehlung_min": "<kuehlung_min>",
      "planpause_min": "<planpause_min>",
      "sonstiger_auszustand_min": "<sonstiger_auszustand_min>",
      "zeiten_disjunkt": "<zeiten_disjunkt>"
    },
    "name": "klimageraet_verlauf_ausfallphasen_ungeklaert"
  }
}

Input Schema

NameRequiredDescriptionDefault
probe_minYesGesamtdauer der kontrollierten Kühlprobe
kuehlung_minYesDauer belegter Kühlphasen
planpause_minYesWeitere Minuten mit bekannter beabsichtigter Pause
zeiten_disjunktYesJede Minute wurde höchstens einer dieser Gruppen zugeordnet
sonstiger_auszustand_minYesWeitere Minuten ausdrücklich beobachtet ohne Kühlung

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 calculation, and the description adds that three downtime categories are balanced separately. However, it does not disclose the return shape, what happens when 'zeiten_disjunkt' is false, or how unresolved downtime is derived versus the explicitly observed 'sonstiger_auszustand_min'.

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 the verb and categories immediately visible. The full German/English duplication adds length without new meaning, but the description remains short and easy to scan.

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?

The schema is rich and fully documented, and the description says the relevant time categories are balanced separately. Because there is no output schema, however, the description should say more about the returned totals or validation behavior when the disjointness flag is false.

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 five parameters are already well defined in the schema. The description adds the conceptual grouping into active, planned, and unresolved time, but does not clarify parameter-level behavior such as how 'sonstiger_auszustand_min' maps to unresolved downtime or how 'zeiten_disjunkt' affects the calculation.

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?

The description gives a specific verb ('Bilanziere') and resource ('Ausfallzeit während einer Kühlprobe') and names the three categories being separated: active cooling, planned pauses, and unresolved downtime. It is clear what the tool computes, but it does not distinguish it from the many similarly named klimageraet siblings.

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 phrase 'während einer Kühlprobe' implies the applicable context, but there is no explicit when-to-use guidance, no exclusions, and no alternative tool named. Usage is inferable rather than stated.

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