Skip to main content
Glama

getecoback-climate-weather

messung_nullanzeige_obergrenze

Read-only

Unveränderte Energieanzeige bei bekanntem Anzeigeverhalten als Obergrenze einordnen — Interpret an unchanged cumulative meter reading without claiming zero consumption.

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": {
      "anzeige_unveraendert": "<anzeige_unveraendert>",
      "schritt_kwh": "<schritt_kwh>",
      "dauer_h": "<dauer_h>",
      "unterlast_erfasst": "<unterlast_erfasst>"
    },
    "name": "messung_nullanzeige_obergrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauer_hYesVerstrichene Messdauer in Stunden.
schritt_kwhYesSchrittweite der Energieanzeige in kWh, laut Gerät.
unterlast_erfasstYesIst die Erfassung auch für diese niedrige Last in der Anleitung belegt?
anzeige_unveraendertYesWar die kumulierte Energieanzeige vom Anfang bis zum Ende unverändert?

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?

The annotations already establish that this is a read-only, closed-world operation, so the safety profile is covered. The description adds meaningful domain behavior by warning that an unchanged reading must not be treated as zero consumption, but it does not explain how the upper bound is computed or what the result looks like.

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?

The definition is compact and front-loads the core interpretation rule. The bilingual wording is slightly repetitive but still efficient and not padded with irrelevant information.

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 read-only analytic tool with four fully described schema parameters, the description gives the essential purpose and an important caveat. However, because there is no output schema, it could do more to explain the expected result or the assumptions behind treating the reading as an upper bound.

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 four required parameters are already fully documented in the input schema. The description adds no additional parameter-level detail, which is acceptable 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 states a specific interpretive operation on an unchanged cumulative meter reading and explicitly frames it as an upper bound rather than zero consumption. It is clear what the tool does, though it does not directly name or distinguish a sibling alternative.

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 intended use is implied by 'bei bekanntem Anzeigeverhalten' and 'als Obergrenze einordnen', suggesting the tool applies when the display behavior is known and the reading did not change. There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance.

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