Skip to main content
Glama

getecoback-raumklima

thermostat_paketkosten

Read-only

Thermostat-Ausstattung für mehrere Heizkörper mit Zentrale und Zubehör budgetieren — Budget radiator thermostat hardware and shared hub.

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": {
      "head_count": "<head_count>",
      "head_eur": "<head_eur>",
      "hubs_eur": "<hubs_eur>",
      "accessories_eur": "<accessories_eur>",
      "annual_running_eur": "<annual_running_eur>"
    },
    "name": "thermostat_paketkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
head_eurYesPreis je Kopf in Euro.
hubs_eurYesGesamtpreis zusätzlich benötigter Zentralen in Euro. Vorhandene kompatible Zentrale: 0.
head_countYesAnzahl zusätzlich benötigter Köpfe (ganze Stückzahl).
accessories_eurYesGesamtpreis der geprüften Adapter und Zubehörteile in Euro.
annual_running_eurYesWiederkehrende Kosten des gesamten Pakets im Jahr in Euro.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say the tool is a pure arithmetic roll-up with no lookup, does not describe what is summed, and – with no output schema – gives no hint about the returned result shape. It is consistent with the annotations, just thin.

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?

One short, front-loaded sentence with no filler. The bilingual German-then-English duplication is redundant for most agents and costs a few tokens, which keeps it from a 5.

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 five fully documented numeric parameters, most of the burden falls on the schema. However, with no output schema, the description should at least indicate what the calculation yields (e.g. total package cost, per-head cost) – that is missing.

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 parameter carries a clear German explanation including the 'existing compatible hub = 0' convention, so the schema does the heavy lifting. The description's only marginal addition is framing the hub as 'shared' across radiators; otherwise it adds no semantic detail beyond the input 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 verb (budget/budgetieren) and a specific resource (thermostat hardware package with heads, hub and accessories), so the purpose is unmistakable. It does not explicitly contrast itself with siblings such as thermostat_amortisation or thermostat_ventilabgleich, so it falls short of 5.

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 only implied by the word 'budgetieren/Budget' – it is for costing a multi-radiator package. There is no statement of when to use this instead of the amortisation or valve-balancing siblings, and no prerequisites or exclusions are given.

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