Skip to main content
Glama

getecoback-climate-weather

kuehlschrank_temperaturprotokoll

Read-only

Wiederholte Temperaturmessungen im gleichen Kühlschrankfach mit deinem Zielband abgleichen. — Check repeated thermometer readings against your target range before changing settings.

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": {
      "morgens_c": "<morgens_c>",
      "mittags_c": "<mittags_c>",
      "abends_c": "<abends_c>",
      "ziel_unten_c": "<ziel_unten_c>",
      "ziel_oben_c": "<ziel_oben_c>"
    },
    "name": "kuehlschrank_temperaturprotokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
abends_cYesStabilisierter Messwert abends am gleichen Messort.
mittags_cYesStabilisierter Messwert mittags am gleichen Messort.
morgens_cYesStabilisierter Messwert am Morgen am gleichen Messort.
ziel_oben_cYesObere Zielgrenze für genau dieses Fach in °C.
ziel_unten_cYesUntere Zielgrenze für genau dieses Fach 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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the meaningful constraint that readings must be repeated and from the same compartment, but says nothing about what the comparison produces or how out-of-band results are reported.

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?

Two short sentences, front-loaded with the core action. However, the German and English sentences are verbatim duplicates of the same content, so half the text earns no additional information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, fully documented, read-only computation tool with no output schema, the description covers the essential preconditions (repeated readings, same compartment, target band). Only the nature of the returned verdict is left implicit, which is a minor 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%, so all five parameters are already documented in the schema. The description reinforces the 'same compartment' and 'target band' semantics that map to ziel_unten_c/ziel_oben_c but adds no format or tolerance details beyond that.

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?

States a specific verb (abgleichen/check) and a specific resource (repeated temperature readings in the same fridge compartment against a target band). It is clearly a diagnostic comparison rather than a settings change, though it does not name or contrast any sibling tool.

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?

'before changing settings' implies the moment to use it, which is useful context. There is no explicit when-not guidance and no named alternative among the many kuehlschrank_* siblings, so the agent must infer the boundary itself.

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