Skip to main content
Glama

getecoback-raumklima

messreihe_haushaltsgeraet_ausreisser

Read-only

Fünf Wiederholungsmessungen derselben Geräteaufgabe auf einen auffälligen Einzelwert prüfen. — Flag an unusual repeat measurement without discarding it automatically.

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": {
      "lauf_1": "<lauf_1>",
      "lauf_2": "<lauf_2>",
      "lauf_3": "<lauf_3>",
      "lauf_4": "<lauf_4>",
      "lauf_5": "<lauf_5>",
      "grenze_kwh": "<grenze_kwh>"
    },
    "name": "messreihe_haushaltsgeraet_ausreisser"
  }
}

Input Schema

NameRequiredDescriptionDefault
lauf_1YesEnergie des ersten Laufs in kWh.
lauf_2YesEnergie des zweiten Laufs in kWh.
lauf_3YesEnergie des dritten Laufs in kWh.
lauf_4YesEnergie des vierten Laufs in kWh.
lauf_5YesEnergie des fünften Laufs in kWh.
grenze_kwhYesDein absoluter Prüfspielraum in kWh, mindestens Auflösung und relevante Messabweichung berücksichtigen.

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. The description adds the useful behavioral nuance that the outlier is flagged and not auto-discarded. It says nothing about how the flag is reported or how the grenze_kwh threshold drives the decision, so it goes beyond annotations only modestly.

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?

Two short sentences, front-loaded with the operation and followed by the key behavioral caveat. The bilingual duplication adds minor redundancy but no padding.

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?

With no output schema, the description never explains what the tool returns or what constitutes the 'auffälliger Einzelwert' relative to grenze_kwh, which matters for a diagnostic check. The core operation and the non-destructive intent are covered, but the result semantics are left implicit.

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 each parameter is already documented, and the description adds no new meaning about lauf_1..lauf_5 or grenze_kwh. Baseline 3 applies when the schema does the heavy lifting.

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 description names a specific verb and resource: check five repeat measurements of the same device task for a single conspicuous value. The English half reinforces the intent ('Flag an unusual repeat measurement'). It does not explicitly contrast with the sibling messreihe_echte_wiederholungen_zaehlen, so it stops short of a 5.

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?

Usage is only implied by the phrase 'without discarding it automatically', which hints that this tool flags data rather than removing it. There is no explicit statement of when to call this versus the sibling counting/zählung tool, and no stated prerequisites.

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