Skip to main content
Glama

getecoback-climate-weather

heissluft_gemeinsam_getrennt_messwert_je_ausgabe

Read-only

Eine gemeinsam gemessene Heißluftnutzung je ausgegebene Portion gegen zwei getrennt gemessene Nutzungen vergleichen — Compare per-serving draw from simultaneous and separate dual-basket use.

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": {
      "beide_kwh": "<beide_kwh>",
      "beide_portionen": "<beide_portionen>",
      "getrennt_kwh": "<getrennt_kwh>",
      "getrennt_portionen": "<getrennt_portionen>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "heissluft_gemeinsam_getrennt_messwert_je_ausgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
beide_kwhYesGemessener Gesamtbedarf bei Nutzung beider zugelassenen Zonen.
getrennt_kwhYesGesamtbedarf der zwei einzeln gemessenen Zonenläufe.
vergleichbarYesSind Rezept, Portionengröße und Endergebnis für diesen Vergleich gleichartig?
beide_portionenYesTatsächlich erhaltene vergleichbare Portionen daraus.
getrennt_portionenYesTatsächlich erhaltene vergleichbare Portionen daraus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 is covered and the bar is lower. The description adds domain context — that two measurement modes are being reconciled on a per-portion basis — but says nothing about the computation performed (division by portions?), what result form comes back, or how a false `vergleichbar` changes the outcome. No output schema exists to cover 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 front-loaded sentence states the comparison immediately, with the English gloss appended. The bilingual duplication is largely redundant for an agent that already sees the German, but it is short and free of filler.

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 comparison tool with fully documented inputs but no output schema, the description should say what is returned (a per-portion ratio, a difference, a verdict) and what happens when `vergleichbar` is false. Neither is covered, so an agent can form the call but not predict or interpret the result.

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 every one of the five parameters carries its own German description, so the description legitimately defers to the schema. It adds no syntax, unit or interaction guidance beyond the schema, which is the baseline-3 case.

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 (vergleichen / compare) on a specific quantity (Heißluftnutzung je ausgegebene Portion) across two measurement regimes (simultaneous dual-basket vs. two separate runs). That is enough to distinguish it from measurement siblings such as heissluft_teilauslastung_messwert_mehrportion, though the dense German phrasing makes the exact quantity being compared slower to parse than it needs to be.

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

Usage Guidelines2/5

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

The description states what the tool compares but gives no when-to-use guidance: no prerequisites, no indication of which sibling to pick when the user has only one basket or only a single measurement, and no note about when the comparison is meaningful. The `vergleichbar` parameter hints that comparability is user-asserted, but the description never tells the agent to check or populate it deliberately.

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