Skip to main content
Glama

getecoback-raumklima

spuelanzeige_externer_zaehler_gleicher_messumfang

Read-only

Einzelanzeige im Gerät und externen Messwert nur auf bestätigtem gleichem Zeitraum gegenüberstellen — Check whether an external meter and the display cover the same cycle.

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": {
      "display_kwh": "<display_kwh>",
      "extern_kwh": "<extern_kwh>",
      "gleicher_lauf": "<gleicher_lauf>",
      "gleicher_zeitumfang": "<gleicher_zeitumfang>",
      "gleicher_energieumfang": "<gleicher_energieumfang>"
    },
    "name": "spuelanzeige_externer_zaehler_gleicher_messumfang"
  }
}

Input Schema

NameRequiredDescriptionDefault
extern_kwhYesExtern gemessene kWh ausschließlich für das bezeichnete Gerät.
display_kwhYesAbgelesener kWh-Wert für den abgeschlossenen Einzellauf.
gleicher_laufYesSind beide Quellen demselben abgeschlossenen Lauf zugeordnet?
gleicher_zeitumfangYesSind identische Zeitgrenzen einschließlich eventuellem Nachlauf belegt?
gleicher_energieumfangYesErfassen beide belegten Werte dieselbe Energieart desselben Geräts?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish a read-only, closed-world operation, while the description adds the useful same-period gating constraint. However, it does not disclose whether false confirmations reject the invocation, produce an ineligible result, or merely suppress the comparison.

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 compact single line front-loads the operation and its key restriction without procedural filler. The bilingual wording is slightly redundant and not perfectly aligned: the German text promises a value comparison, whereas the English text describes only a same-cycle check.

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?

The schema and annotations make the five required inputs understandable, but there is no output schema and the description does not define the returned result or mismatch behavior. The prose also emphasizes only period or cycle alignment, omitting the schema's separate same-energy-scope condition.

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 the fields already document the two kWh readings and confirmations for the same run, time boundaries, and energy scope. The description reinforces their shared-cycle relationship but adds no further evidence requirements or flag semantics, so the high-coverage baseline 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 description gives a concrete action and resources: comparing the appliance's individual display with an external measurement, then checking whether both cover the same cycle. This is clear and narrowly scoped, but it does not explicitly distinguish the tool from any sibling workflow.

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

Usage Guidelines4/5

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

The phrase "nur auf bestätigtem gleichem Zeitraum" supplies an explicit precondition and warns against comparing values unless the period is confirmed to match. It does not identify an alternative when the run, time boundaries, or energy scope differ, or explain the next step after a failed check.

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