Skip to main content
Glama

getecoback-raumklima

reiniger_zeitgewinn_gegen_aufpreis

Read-only

Bewerten, welchen eigenen Mindestwert je gesparter Stunde ein Reinigungsgeräte-Aufpreis benötigt — Quantify the break-even personal value per hour of active cleaning time saved.

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": {
      "aufpreis_eur": "<aufpreis_eur>",
      "minuten_alt": "<minuten_alt>",
      "minuten_neu": "<minuten_neu>",
      "einsaetze": "<einsaetze>"
    },
    "name": "reiniger_zeitgewinn_gegen_aufpreis"
  }
}

Input Schema

NameRequiredDescriptionDefault
einsaetzeYesVorgesehene Anzahl gleichwertiger Einsätze.
minuten_altYesAktive Minuten pro gleichwertigem Einsatz für den alten Weg, inklusive Pflege.
minuten_neuYesAktive Minuten für den neuen Weg, inklusive Pflege.
aufpreis_eurYesKaufpreisaufschlag für den neuen Weg 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, so the agent knows this is a side-effect-free, closed-domain computation. The description reinforces that it is a pure quantification, but it does not disclose the result's unit/shape (presumably EUR per saved hour) or the underlying assumption that the surcharge amortizes linearly over 'einsaetze'. With annotations covering safety, this is adequate but not rich.

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 front-loaded sentence with no filler, though the German and English halves are near-verbatim duplicates of the same claim rather than complementary information. Efficient, with minor redundancy.

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?

There is no output schema, so the description carries the burden of saying what is returned, and it only gestures at 'break-even personal value per hour' without specifying units, formula direction, or how the result should be interpreted. For a four-parameter derived-metric tool, one more sentence on the returned quantity would close the gap.

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 schema, including the 'inklusive Pflege' scope of the minute fields. The description adds only the conceptual frame ('per saved hour', 'active cleaning time'), which the schema largely covers. Baseline 3 applies.

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 states a specific computation: deriving the break-even personal value per saved hour implied by a cleaning-device price surcharge. The verb ('Bewerten/Quantify') and the derived quantity are both named, so an agent knows what the tool produces. It does not distinguish itself from similarly shaped siblings such as geraet_bundle_aufpreis_gebrauchswert or kuehlloesung_uebergangsbudget_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description makes clear this is a break-even/valuation calculation, which suggests when it applies, but it never states preconditions or when a sibling valuation tool would be the better choice. There is no explicit when-not guidance.

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