Skip to main content
Glama

getecoback-climate-weather

nutzwaerme_kostenvergleich

Read-only

Zwei Wärmeerzeuger für dieselbe abgegebene Nutzwärme vergleichen — Compare variable costs for an equal amount of delivered heat.

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": {
      "useful_kwh": "<useful_kwh>",
      "factor_a": "<factor_a>",
      "factor_b": "<factor_b>",
      "price_a": "<price_a>",
      "price_b": "<price_b>"
    },
    "name": "nutzwaerme_kostenvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
price_aYesArbeitspreis in EUR/kWh.
price_bYesArbeitspreis in EUR/kWh.
factor_aYesNutzwärme je kWh Einsatz für A im Zeitraum.
factor_bYesNutzwärme je kWh Einsatz für B im Zeitraum.
useful_kwhYesBenötigte Nutzwärme im Vergleichszeitraum in kWh.

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 is covered. The description usefully scopes the calculation to *variable* costs (implying capital/investment costs are excluded), but says nothing about what is returned (per-variant costs, difference, savings) despite no output schema existing.

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 the German original followed by an English rendering; efficient, though the bilingual duplication adds a little redundancy without new information.

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 calculation tool with fully documented inputs, the definition is nearly sufficient, but with no output schema it should indicate the result shape (e.g. cost A, cost B, delta in EUR) 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% with units and min/max bounds per parameter, so the schema carries most semantics. The description still adds the key framing that useful_kwh is the shared delivered-heat quantity for both variants, clarifying the relationship between the factor and price pairs.

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?

States a specific operation: comparing variable costs of two heat generators for the same delivered useful heat, which separates it from siblings like sparbrause_kostenvergleich or bauteil_waermeverlust. It does not explicitly name an alternative, but the verb+resource are precise.

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 comparison scenario is implied clearly ('zwei Wärmeerzeuger ... vergleichen'), but there is no explicit when-to-use versus when-not guidance, nor any pointer to related tools such as geraetewechsel_rechnen for full replacement economics.

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