Skip to main content
Glama

getecoback-raumklima

energielabel_messwert_abgleichen

Read-only

Energieetikett und eigene Messreihe bei gleicher Anzahl vergleichbarer Zyklen abgleichen. — Compare EU label cycle energy with household measurements for the same type of 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": {
      "label_kwh_je_100": "<label_kwh_je_100>",
      "gemessen_kwh": "<gemessen_kwh>",
      "gemessene_zyklen": "<gemessene_zyklen>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "energielabel_messwert_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gemessen_kwhYesEnergie deiner beobachteten Zyklen zusammen in kWh.
vergleichbarYesProgramm, Beladung und Ergebnis sind für den Szenarienvergleich hinreichend ähnlich.
gemessene_zyklenYesAnzahl beobachteter Zyklen.
label_kwh_je_100YesEnergie laut Label in kWh je 100 Zyklen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety profile is covered. The description adds the precondition of equal, comparable cycle counts, but says nothing about what the comparison produces (deviation, verdict, ratio) despite there being 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler. The English half largely restates the German rather than adding information, which costs a small amount of efficiency but aids comprehension.

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?

All four required parameters are schema-documented and the core precondition is stated, but for a pure computation tool with no output schema, the description should indicate what result is returned (e.g. deviation per 100 cycles) so an agent knows what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description still reinforces the linkage between the label value and the measurement series at matched cycle counts. The German/English mismatch ('gleiche Anzahl vergleichbarer Zyklen' vs 'same type of cycle') slightly blurs whether cycle count or cycle type is the binding constraint.

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 concrete verb (abgleichen/compare) and two specific resources: the EU energy label value and the household measurement series. It is distinguishable from label-only or measurement-only siblings, though it never explicitly names an alternative tool.

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: the tool applies when the measured cycles are comparable in count and program/load to the label scenario. No explicit when-not-to-use condition or named alternative (e.g. a pure measurement-evaluation sibling) is given, so the agent must infer selection criteria.

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