Skip to main content
Glama

getecoback-raumklima

geraet_reparaturpreis_grenze

Read-only

Bei einem Defekt den maximal vergleichbaren Reparaturpreis für einen festgelegten Nutzungszeitraum bestimmen. — Find the repair quote at which repairing and replacing would have equal costs over a shared horizon.

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": {
      "reparaturangebot": "<reparaturangebot>",
      "neukaufpreis": "<neukaufpreis>",
      "alt_kwh_jahr": "<alt_kwh_jahr>",
      "neu_kwh_jahr": "<neu_kwh_jahr>",
      "jahre": "<jahre>",
      "strompreis": "<strompreis>",
      "reparaturdauer_bestaetigt": "<reparaturdauer_bestaetigt>"
    },
    "name": "geraet_reparaturpreis_grenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
jahreYesFür beide Optionen angesetzte verbleibende Vergleichsjahre.
strompreisYesBruttoarbeitspreis in €/kWh.
alt_kwh_jahrYesGeschätzter Jahresverbrauch des reparierten Geräts.
neu_kwh_jahrYesGeschätzter Jahresverbrauch des Ersatzgeräts.
neukaufpreisYesVollständiger Preis eines funktional passenden Ersatzes nach Abzug sicherer Erlöse.
reparaturangebotYesReparaturangebot einschließlich Arbeit, Teilen und Anfahrt.
reparaturdauer_bestaetigtYesEine ausreichende weitere Nutzungsdauer nach Reparatur ist für das Szenario plausibel begründet.

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 an offline, side-effect-free calculation and the description only needs to add context. It does explain what the result represents (an indifference price), but it omits a meaningful behavioral trait: reparaturdauer_bestaetigt acts as a plausibility gate, and the description never says whether a false value blocks the calculation or alters the result.

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 core idea is front-loaded in the first sentence, but the definition is a German sentence immediately restated in English, so the same information is delivered twice with no added nuance. Functionally clear, but a third of the text is duplication.

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 seven-parameter pure calculation with no output schema, the description conveys the decision model well enough to call it correctly. The remaining gap is the semantics of the confirmation flag and the shape of the returned threshold, which the description leaves implicit.

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%, with every one of the seven parameters documented in the schema, so the baseline is 3. The description adds conceptual framing (a shared horizon, energy cost over both options) but no parameter-level detail 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?

States a specific computation: the repair quote at which repairing and replacing cost the same over a defined horizon. The verb+resource is concrete enough to distinguish it from siblings like geraet_testzitat_einordnen, but it never names or contrasts a sibling explicitly.

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?

The opening 'Bei einem Defekt' gives a usage scenario, so the agent knows this applies to a broken device weighing repair vs. replacement. There is no when-not guidance, no named alternative, and no note on what to do if the economic comparison is not the deciding factor.

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