Skip to main content
Glama

getecoback-climate-weather

geraete_gebraucht_restnutzungs_schwelle

Read-only

Mindestzahl gleichwertiger Einsätze berechnen, die ein Gebrauchtgerät für denselben Anschaffungspreis pro Einsatz erreichen müsste — Find the used appliance usage threshold relative to a new one.

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": {
      "gebraucht_eur": "<gebraucht_eur>",
      "neu_eur": "<neu_eur>",
      "neu_einsaetze": "<neu_einsaetze>",
      "gebraucht_einsaetze": "<gebraucht_einsaetze>"
    },
    "name": "geraete_gebraucht_restnutzungs_schwelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
neu_eurYesZahlung für ein gleich nutzbares Neugerät.
gebraucht_eurYesZahlung für das einsatzbereite Gebrauchtgerät.
neu_einsaetzeYesEigene Szenario-Anzahl Einsätze für das Neugerät.
gebraucht_einsaetzeYesEigene erwartete verbleibende Einsätze des Gebrauchtgeräts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety profile is covered. The description usefully clarifies the underlying model — the threshold is defined relative to equal acquisition price per use — but says nothing about edge cases such as a zero or very low remaining-use count, or whether an infeasible comparison yields an error or a sentinel value.

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 clauses, verb-first and front-loaded, with the English sentence acting as a compact gloss rather than padding. The bilingual duplication is mild redundancy but aids disambiguation, so it is not wasteful.

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?

All four inputs are fully documented by the schema and the safety annotations are adequate, but there is no output schema, so the description should have stated what the computed result looks like (a count of uses, a rounded threshold, a ratio). That return-value gap is the main missing piece for a pure calculation 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% with units, ranges and per-field meanings for all four required parameters, so the schema carries the parameter burden. The description adds only the conceptual relationship (same acquisition price per use) and does not map inputs to the formula, so the 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?

States a specific verb ("Mindestzahl ... berechnen") and a specific quantity (the number of equivalent uses a used appliance must reach to match the new device's cost per use). The English gloss reinforces the concept, so an agent knows this is a break-even usage calculator rather than a measurement or lookup tool. It does not name or contrast any sibling, which keeps it out of the 5 band.

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 explicit when-to-use statement, no prerequisites, and no alternatives. The framing ("für denselben Anschaffungspreis pro Einsatz") hints at a used-vs-new purchase decision, but the agent must infer the decision context entirely from the phrasing.

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