Skip to main content
Glama

getecoback-raumklima

gefrierschrank_klimaband_besuchsminimum_referenzpunkt

Read-only

Trenne einen protokollierten kalten Aufstellpunkt von einem gleichzeitig wärmeren Raumreferenzwert — Separate a cold freezer placement reading from an in-room reference

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": {
      "genaues_modell": "<genaues_modell>",
      "lufteintritt_min_c": "<lufteintritt_min_c>",
      "referenz_zeitgleich_c": "<referenz_zeitgleich_c>",
      "gemeinsame_uhr_und_ort": "<gemeinsame_uhr_und_ort>"
    },
    "name": "gefrierschrank_klimaband_besuchsminimum_referenzpunkt"
  }
}

Input Schema

NameRequiredDescriptionDefault
genaues_modellYesGenaue deutsche Modellkennung
lufteintritt_min_cYesNiedrigste dokumentierte Lufttemperatur direkt am künftig betrachteten Aufstellpunkt
referenz_zeitgleich_cYesWert im gleichen Moment am zentralen Raumreferenzpunkt
gemeinsame_uhr_und_ortYesKaltpunkt und Referenz wurden gleichzeitig als Luftmessung belegt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 the safety profile is known without the description. The description adds only a restatement of the inputs (cold point vs. warmer reference) and says nothing about what the separation yields, whether a tolerance or threshold applies, or how the result should be interpreted — the behavioral burden for a computation-style tool remains largely unaddressed.

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?

A single front-loaded sentence with no filler, and the German/English duplication is defensible for a bilingual tool name. The only inefficiency is that the mirrored translation consumes space without adding information.

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?

There is no output schema, so the description is the only place that could explain what the tool returns or how the cold-vs-reference separation is expressed, and it is silent on that. For a read-only computation with four required parameters, the definition leaves the agent guessing about the result.

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%, with all four parameters, ranges, and the model enum fully documented in the schema itself. The description adds no syntax, units, or interpretation beyond what the schema already states, so the baseline 3 applies.

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 does name a verb ('Trenne'/'Separate') and two resources (a logged cold placement reading and a simultaneous in-room reference value), so the domain is discernible. However, 'separate' is ambiguous about what operation actually occurs (comparison, subtraction, classification) and the framing says nothing about the tool name's 'Besuchsminimum'/'Klimaband' outcome, so it does not clearly distinguish this from reference-point siblings such as rasenroboter_randprobe_referenzpunkt_vor_nach.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, when not to, or which sibling handles a related measurement. The only implicit constraint is that both readings must be simultaneous, and that is already carried by the required parameter 'gemeinsame_uhr_und_ort'.

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