Skip to main content
Glama

getecoback-climate-weather

thermostat_amortisation

Read-only

Sparannahme und Amortisation eines Thermostats prüfen — Estimate thermostat payback using your own savings assumption.

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": {
      "base": "<base>",
      "saving": "<saving>",
      "cost": "<cost>",
      "running": "<running>"
    },
    "name": "thermostat_amortisation"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYesJährliche beeinflussbare Heizkosten in Euro.
costYesEinmalkosten in Euro.
savingYesEigene Annahme für Einsparung in Prozent.
runningYesJährliche Zusatzkosten in Euro.

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, and the description is consistent with a pure, non-mutating estimate. Beyond that it adds only that the calculation is driven by a caller-supplied assumption; it says nothing about what is returned (payback period, absolute savings) despite there being no output schema.

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 tight sentence, front-loaded with the German phrasing and immediately restated in English for disambiguation. The bilingual duplication is minor overhead but earns its place given ambiguous siblings.

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 numeric parameters with no output schema mean the description should at least sketch what the result represents (e.g., years to payback versus annual euro savings). It conveys the input concept but leaves the returned value undefined for a calculator tool.

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 (base, saving, cost, running) already carry German descriptions in the schema. The description only echoes the 'own savings assumption' idea that maps to the saving parameter, adding no units, bounds, or interaction details 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 gives a specific verb and resource: 'Sparannahme und Amortisation eines Thermostats prüfen' / 'Estimate thermostat payback', which tells an agent this computes amortisation from a savings assumption. It is clear but does not distinguish itself from calculation-oriented siblings such as geraetewechsel_rechnen or thermostat_paketkosten.

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?

'using your own savings assumption' implies the selection condition — use this when the agent supplies a user-specific saving percentage rather than a built-in default — but this is inferred rather than stated. There is no explicit when-not guidance or named alternative.

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