Skip to main content
Glama

getecoback-climate-weather

raumthermometer_mitfuehren_abweichungsrichtung_wechsel

Read-only

Erkenne, ob ein mitgeführtes Thermometer nach dem Ablegen gegenüber der festen Referenz die Abweichungsrichtung wechselte — Check whether a carried thermometer’s offset changed sign after placement

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": {
      "tragbar_frueh_c": "<tragbar_frueh_c>",
      "referenz_frueh_c": "<referenz_frueh_c>",
      "tragbar_spaet_c": "<tragbar_spaet_c>",
      "referenz_spaet_c": "<referenz_spaet_c>",
      "toleranz_c": "<toleranz_c>",
      "ort_und_uhr_passen": "<ort_und_uhr_passen>"
    },
    "name": "raumthermometer_mitfuehren_abweichungsrichtung_wechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranz_cYesEigene kombinierte Toleranz für Abweichungen von der Referenz
tragbar_frueh_cYesErste Ablesung des abgelegten tragbaren Sensors
tragbar_spaet_cYesSpätere Ablesung des unveränderten tragbaren Sensors
referenz_frueh_cYesZeitgleiche erste Referenz am selben Platz
referenz_spaet_cYesZeitgleiche spätere Referenz am selben Platz
ort_und_uhr_passenYesKontrollmessungen am selben Ort mit gemeinsamer Uhr und ohne Berührung

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 the safety profile is covered and the description only needs to add context. It explains the sign-change concept, which is useful, but never mentions the caller-supplied tolerance or the ort_und_uhr_passen gate input, both of which materially affect the verdict. It also does not say what kind of result is produced, and there is no output schema to fall back on.

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 statement of the check, immediately followed by an English rendering of the same sentence. Nothing is wasted, though the bilingual duplication adds length without adding information for an agent that already parses one language.

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?

For a six-parameter, all-required computation with no annotations about return values and no output schema, the description covers the core comparison but omits two things an agent needs: the role of the tolerance parameter in deciding a sign change, and the shape of the result. It is adequate to know what is being tested, not fully adequate to call it confidently.

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 every parameter carries a German description, so the schema carries the semantic load. The description only restates the reference-versus-carried relationship and adds nothing about tolerance semantics or how the boolean gate interacts with the numeric readings. Baseline 3 is appropriate.

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 and predicate: detect whether a carried thermometer's offset changed sign versus a fixed reference after placement. That is far more precise than a restatement of the name. It stops short of 5 because it gives no hint of how this differs from the many sibling 'wechsel' tools in the catalog.

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 description embeds the scenario (measure before and after placement, compare against a fixed reference), which implies when the tool applies. However, there is no explicit when-to-use statement, no prerequisites, and no named alternative for a related check such as a plain absolute-offset comparison.

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