Skip to main content
Glama

getecoback-climate-weather

geblaese_leistungsangabe_betriebsart

Read-only

Bei Klimageräten auf einen Verbrauchswert für die richtige Betriebsart achten und unklare Werte vor einer Kostenschätzung aussortieren — Identify whether an input-power figure refers to fan-only or compressor cooling.

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": {
      "benoetigt": "<benoetigt>",
      "ausgewiesen": "<ausgewiesen>",
      "wert_w": "<wert_w>",
      "bezug_geprueft": "<bezug_geprueft>"
    },
    "name": "geblaese_leistungsangabe_betriebsart"
  }
}

Input Schema

NameRequiredDescriptionDefault
wert_wYesEingangsleistung laut Prüf- oder Modellunterlage in Watt.
benoetigtYesBetriebsart, für die geplant werden soll.
ausgewiesenYesBetriebsart laut Quelle für diesen Leistungswert.
bezug_geprueftYesIst elektrische Aufnahme für dieses Modell bestätigt statt abgegebener Kühlleistung?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, local, side-effect-free check. The description adds the useful framing that the result gates a later cost estimate, but says nothing about how ambiguous or conflicting inputs are resolved. No contradiction with the read-only annotation.

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?

Short and front-loaded, with the operative condition (correct operating mode) stated first. The German and English sentences largely restate the same content, which is mild redundancy but defensible for a bilingual toolset.

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?

Four required parameters and no output schema, so the description should hint at what the classification returns; it only implies an identification result without saying whether that is a boolean, a label, or a verdict plus reason. For a self-contained four-parameter check the description is adequate but leaves the return shape to inference.

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% with typed fields and two enums, so the schema already carries the parameter burden and a 3 is the baseline. The description adds the conceptual distinction between fan and cooling modes but does not explain how 'kombinationswert' or 'bezug_geprueft' should be interpreted beyond their schema text.

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 English half states a concrete classification task: decide whether an input-power figure refers to fan-only or compressor cooling. It also names the downstream purpose (filtering unclear values ahead of a cost estimate), which separates it from cost-estimation siblings without naming one explicitly.

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 description gives a clear trigger context — call it before a cost estimate when a consumption value's operating mode is ambiguous ('unklare Werte vor einer Kostenschätzung aussortieren'). It stops short of naming an alternative tool or stating an explicit when-not condition.

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