Skip to main content
Glama

getecoback-raumklima

thermostat_erprobung_wiederverwendungskosten

Read-only

Beim Thermostatversuch mit einem Raum unterscheiden, was bei einem Ausbau weiter nutzbar ist und welche Kosten zusätzlich bleiben — Compare pilot and direct expansion costs after crediting confirmed reusable components.

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": {
      "pilot_eur": "<pilot_eur>",
      "reuse_eur": "<reuse_eur>",
      "direkt_eur": "<direkt_eur>",
      "generation_gleich": "<generation_gleich>"
    },
    "name": "thermostat_erprobung_wiederverwendungskosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
pilot_eurYesAusgaben für einen tatsächlich vergleichbaren Ein-Raum-Versuch.
reuse_eurYesDavon belegbarer Wert der Komponenten, die Käufe im Ausbau ersetzen.
direkt_eurYesKomplette Kosten des geplanten Mehrraum-Ausbaus ohne Versuch.
generation_gleichYesIst die Weiterverwendung genau dieser Generation für den geplanten Ausbau geklärt?

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?

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a safe, self-contained calculation, so the description's burden is lower. It usefully adds a behavioral rule — only demonstrably confirmed reusable value is credited — but says nothing about what the tool returns (a delta, a verdict, a breakdown) even though 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.

Conciseness3/5

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

The purpose clause is front-loaded, which is good, but the sentence is split across two languages and the English half largely re-translates the German half instead of adding new information. Every word is on-topic, yet the em-dash construction costs length without proportional gain.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, fully required, closed-world calculation with no nested objects, the definition covers the inputs and the crediting rule adequately, and the annotations carry the safety profile. The one remaining gap is the shape of the result, which an agent may want to know before promising the user a cost comparison.

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 four parameters are already documented in the input schema, which sets the baseline at 3. The description restates the credit logic already present in reuse_eur's description and adds no new constraint, unit, or edge-case semantics beyond the schema.

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 (comparing pilot versus direct expansion costs after crediting reusable components) on a specific resource, which is clearly distinguishable from a plain amortisation or package-cost tool. It stops short of naming any sibling to route against, and the German and English sentences partially restate the same purpose rather than sharpening it.

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 implied: apply it when a single-room pilot test exists and its reusable parts must be credited against the full multi-room build-out cost. The precondition that reuse must be 'confirmed'/'belegbar' is hinted at and surfaced through the generation_gleich parameter, but there is no explicit when-not guidance and no reference to alternatives such as thermostat_amortisation or thermostat_paketkosten.

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