Skip to main content
Glama

getecoback-raumklima

led_energielabel_1000_stunden_aufgerundet_pon

Read-only

Die auf ganze kWh je 1.000 Stunden aufgerundete Ein-Zustandsangabe gegen einen passenden dezimalen Wattwert halten — Check rounding coherence rather than reading the label as exact watts or annual energy.

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_1000h": "<label_kwh_1000h>",
      "datenblatt_pon_w": "<datenblatt_pon_w>",
      "selbe_lichtquelle_und_betriebsbasis": "<selbe_lichtquelle_und_betriebsbasis>"
    },
    "name": "led_energielabel_1000_stunden_aufgerundet_pon"
  }
}

Input Schema

NameRequiredDescriptionDefault
label_kwh_1000hYesGanzzahliges Feld kWh/1.000 h im Ein-Zustand, nicht Jahresverbrauch.
datenblatt_pon_wYesDeklarierter dezimaler Leistungswert P_on derselben Lichtquelle in W.
selbe_lichtquelle_und_betriebsbasisYesAngebot, Datenblatt, Modellkennung und Ein-Zustand sind eindeutig dieselben?

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 that this is a coherence check rather than an exact-value read, which is useful framing. It does not say what the tool returns on a mismatch (tolerance, verdict shape), and there is no output schema to fill that gap.

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?

A single dense sentence that front-loads the rounding constraint and then states the check and its contrast case. No filler, though the German phrasing is compact to the point of being slightly hard to parse on first read.

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 three-required-parameter read-only check with full schema coverage, the description covers the inputs and the intent adequately. The notable gap is the result: with no output schema, the description should indicate what a pass/fail or tolerance outcome looks like, and it does not.

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 three parameters are already documented, including that the kWh field is per 1,000 h in the on-state and not annual consumption. The description reinforces the rounding relationship between the two numeric inputs but adds no format, tolerance, or unit detail beyond the schema. Baseline 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 description names a specific operation: holding the rounded-up whole-kWh/1,000 h label value against a matching decimal P_on watt value, i.e. a rounding-coherence check. It also explicitly rules out the misreading (exact watts or annual energy), which sharpens what the tool is. It does not name a sibling such as energielabel_messwert_abgleichen, so differentiation is by concept rather than by 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?

The clause 'Check rounding coherence rather than reading the label as exact watts or annual energy' gives a clear when-to-use context and an implicit when-not. However, it frames the exclusion as an interpretation error rather than routing the agent to an alternative tool, and no prerequisites or preconditions are stated.

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