Skip to main content
Glama

getecoback-raumklima

raumlogger_sprung_simultane_referenzbewertung

Read-only

Entscheide, ob ein kurzer Messsprung auch in der zeitgleichen Kontrollreihe zu sehen war — Identify a brief anomaly present only in one room logger

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": {
      "sprung_messung_c": "<sprung_messung_c>",
      "sprung_referenz_c": "<sprung_referenz_c>",
      "abweichung_zur_basis_danach_c": "<abweichung_zur_basis_danach_c>",
      "toleranz_c": "<toleranz_c>",
      "zeitreihen_abgeglichen": "<zeitreihen_abgeglichen>"
    },
    "name": "raumlogger_sprung_simultane_referenzbewertung"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranz_cYesGemeinsame selbst gesetzte Toleranz in °C
sprung_messung_cYesVorzeichen des Sprungs im hauptsächlich genutzten Sensor in °C
sprung_referenz_cYesZeitgleich beobachtete Änderung am benachbarten Kontrollsensor in °C
zeitreihen_abgeglichenYesGerätepositionen, Ablesezeitpunkte und Reaktionszeiten sind ausreichend vergleichbar
abweichung_zur_basis_danach_cYesVorzeichen des Restabstands des Hauptsensors zu dessen Ausgangswert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safety is covered. Beyond that, the description says nothing about how the decision is reached (how the tolerance or the post-jump baseline deviation factor in), nor about the shape of the verdict returned, which matters since there is no output schema.

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?

It is short and front-loaded with the decision, which is good. But the bilingual restatement is not a translation of the same claim — the two halves differ in meaning, so the second half adds ambiguity rather than reinforcement.

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?

This is a five-parameter decision tool with no output schema, and the description never explains the decision rule linking the measurement jump, reference jump, tolerance, and post-baseline deviation, nor what result comes back. An agent knows the topic but not how to interpret or trust the verdict.

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, including units and ranges, are already documented in the schema. The description adds no additional meaning about how these values combine into the decision, so the baseline of 3 applies.

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 German clause names a specific decision ("Entscheide, ob ein kurzer Messsprung auch in der zeitgleichen Kontrollreihe zu sehen war") with a concrete verb and resource, which is far more informative than the name alone. However, the English half ("Identify a brief anomaly present only in one room logger") points in a subtly different direction than the German (jump also present in the reference series), so the two halves do not reinforce one another cleanly.

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 call this versus related siblings such as raumlogger_ereignis_raster_grenzfall or stromzaehler_sprung_leistungsplausibilitaet, and no stated preconditions or exclusions. The agent can only infer the usage context from the decision framing 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