Skip to main content
Glama

getecoback-climate-weather

kaufangebot_rueckgabe_szenario_budget

Read-only

Maximale eigene Kosten eines ausdrücklich kalkulierten Rückgabe-Szenarios mit neuem Kauf gegenüber dem direkten passenden Kauf berechnen — Estimate a return-and-rebuy budget from confirmed fees and refund assumptions.

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": {
      "zahlung_eur": "<zahlung_eur>",
      "erstattung_eur": "<erstattung_eur>",
      "ruecksendung_eur": "<ruecksendung_eur>",
      "ersatz_eur": "<ersatz_eur>",
      "kosten_belegt": "<kosten_belegt>"
    },
    "name": "kaufangebot_rueckgabe_szenario_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
ersatz_eurYesBestätigte Gesamtkosten der Alternative.
zahlung_eurYesTatsächlich im Szenario zu zahlender Gesamtbetrag für den ersten Kauf.
kosten_belegtYesRückgabebedingungen, Erstattung und Zusatzkosten für das genaue Angebot bekannt?
erstattung_eurYesUnter diesen Bedingungen belegter Erstattungsbetrag.
ruecksendung_eurYesEigene belegte Rückgabekosten zusätzlich zur ersten Zahlung.

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 safety profile is covered. The description adds that the estimate is an upper bound derived from confirmed fees and refund assumptions, which is useful context, but it never states what the tool does when kosten_belegt is false (refuse, warn, or return a conditional result) — the single most important behavioral question for a gated calculation tool.

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 front-loaded sentence with the core action first, followed by an English restatement. The bilingual duplication is slightly redundant but the sizing is appropriate and nothing is buried.

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 explaining the returned value — yet it never states the calculation (e.g. whether the budget is payment minus refund plus return cost capped by the replacement cost). For a five-parameter, fully-required financial estimation tool, the core formula and the handling of a negative kosten_belegt remain unexplained.

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 every parameter already carries a German semantic description; baseline 3 applies. The description's phrase 'confirmed fees and refund assumptions' maps loosely to the erstattung_eur/ruecksendung_eur/kosten_belegt semantics but adds no new per-parameter meaning such as the comparison logic against ersatz_eur.

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 concrete verb (berechnen) and a specific artifact (maximale eigene Kosten eines Rückgabe-Szenarios mit neuem Kauf gegenüber dem direkten passenden Kauf). An agent can tell this is a scenario-budget calculation, though it does not explicitly contrast itself with any sibling tool.

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?

Implicit usage is conveyed by 'ausdrücklich kalkulierten Rückgabe-Szenarios' and 'confirmed fees and refund assumptions', i.e. use only when return conditions are documented. No explicit when-not condition or named alternative is given, so an agent must infer the boundary from the wording.

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