Skip to main content
Glama

getecoback-raumklima

luftkuehler_kuehlakku_vor_nach_gegen_wasserprobe

Read-only

Trennt den Zusatznutzen eines Kühlakkus vor und nach dem belegten Ende seiner Kältephase — Compare a cooling pack’s early and late added effect against water-only readings.

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": {
      "frueh_c": "<frueh_c>",
      "spaet_c": "<spaet_c>",
      "wasser_frueh_c": "<wasser_frueh_c>",
      "wasser_spaet_c": "<wasser_spaet_c>",
      "phasen_belegt": "<phasen_belegt>"
    },
    "name": "luftkuehler_kuehlakku_vor_nach_gegen_wasserprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
frueh_cYesLuftstromwert am Nutzplatz in der frühen erprobten Akkuphase in °C.
spaet_cYesEntsprechender Wert nach Ende dieser Phase in °C.
phasen_belegtYesVergleichbare Betriebszustände, Akkuphase und Raumwerte dokumentiert?
wasser_frueh_cYesWasserprobe ohne Akku mit passendem frühem Messpunkt in °C.
wasser_spaet_cYesWasserprobe ohne Akku mit passendem spätem Messpunkt in °C.

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 annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the comparison is against a water-only baseline at matched early/late points, which is real behavioral context, but with no output schema it never says what the result looks like (a delta? a verdict? two values?).

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?

One compact sentence, front-loaded with the core comparison and followed by a baseline clarification. The German/English duplication is slightly redundant but reinforces the key framing 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?

Inputs are fully specified and required-count is high, but the tool has no output schema and the description does not describe the returned quantity or its interpretation. For an analysis tool whose value is the resulting comparison, that is a meaningful gap.

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% and all five parameters are individually documented with units and ranges, so the description carries no obligation. It conveys only the pairing concept (early vs. late, pack vs. water), which the schema names largely already imply.

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?

Names a specific operation (separating a cooling pack's added effect before vs. after the documented end of its cold phase) and a concrete baseline (water-only readings). It is distinguishable from the sibling cooling-pack tools, though the phrasing 'Trennt den Zusatznutzen' is abstract enough that the agent must read the schema to know what is being computed.

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 prerequisite 'belegten Ende seiner Kältephase' and the required flag phasen_belegt imply the comparison is only valid when comparable operating states and the cooling phase are documented, but this is never stated as a condition for use. No alternatives are named and no when-not guidance is given, so usage is only implied.

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