Skip to main content
Glama

getecoback-climate-weather

kuehlloesung_uebergangsbudget_gegen_aufpreis

Read-only

Eigene Kosten einer Zwischenlösung einer sofort verfügbaren Klimageräte-Alternative gegenüberstellen — Compare bridging costs with the premium for a verified immediate alternative.

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": {
      "wunsch_eur": "<wunsch_eur>",
      "sofort_eur": "<sofort_eur>",
      "uebergang_eur": "<uebergang_eur>",
      "aufstellung_belegt": "<aufstellung_belegt>"
    },
    "name": "kuehlloesung_uebergangsbudget_gegen_aufpreis"
  }
}

Input Schema

NameRequiredDescriptionDefault
sofort_eurYesBestätigte Gesamtkosten des aktuellen Alternativangebots.
wunsch_eurYesAngenommene spätere Gesamtkosten der Wunschlösung.
uebergang_eurYesEigene erwartete Ausgaben für die Zwischenlösung bis dahin.
aufstellung_belegtYesSind beide Optionen für die beabsichtigte Aufstellung überprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds almost nothing beyond that: it does not say what the comparison yields (a delta, a verdict, or a recommendation), nor what happens when 'aufstellung_belegt' is false despite the precondition wording.

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 sentences with the core comparison front-loaded and no filler. The bilingual duplication is mildly redundant but serves clarity for a German-named tool.

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?

This is a low-complexity read-only calculation with fully documented parameters and no output schema, so the bar is modest. Still, the description leaves the agent guessing about the result shape and about the consequence of the verification flag, which matters given all four parameters are required.

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 with units and bounds. The description's framing of 'bridging costs' versus 'premium' loosely maps onto uebergang_eur and the sofort/wunsch pair but adds no syntax or interpretation guidance 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 (gegenüberstellen/compare) and two concrete quantities: own bridging costs for an interim solution versus the premium of an immediately available, verified alternative. An agent can tell what is being compared, though it is not explicitly differentiated from similarly shaped siblings such as reiniger_zeitgewinn_gegen_aufpreis.

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?

There is no statement of when this tool should be chosen, when it should not, or what alternatives exist for adjacent cost comparisons. The scenario ('sofort verfügbare Alternative') hints at usage but no explicit routing guidance is 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