Skip to main content
Glama

getecoback-climate-weather

angebot_rabatt_ungeplante_fuellerkosten

Read-only

Einen belegten Rabatt gegen zusätzlich nötigen, ungeplanten Warenkorbwert aufrechnen — Test a coupon against items you would not otherwise buy.

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": {
      "sollkorb_eur": "<sollkorb_eur>",
      "mindestwert_eur": "<mindestwert_eur>",
      "zusatz_eur": "<zusatz_eur>",
      "rabatt_eur": "<rabatt_eur>",
      "bedingungen_geprueft": "<bedingungen_geprueft>"
    },
    "name": "angebot_rabatt_ungeplante_fuellerkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
rabatt_eurYesGesamtrabatt, der laut Bedingungen für den so gefüllten Korb gilt.
zusatz_eurYesKosten der erforderlichen Zusatzartikel, die nicht auf dem Einkaufsplan waren.
sollkorb_eurYesWarenwert des tatsächlich geplanten Einkaufs ohne Versand.
mindestwert_eurYesBelegter Mindestwarenwert für genau diesen Rabatt.
bedingungen_geprueftYesArtikelberechtigung, Rabattbetrag und unterschiedliche Versandkosten geprüft; Versandkosten sind in beiden Fällen gleich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 by structured data. The description adds that the discount must be 'belegt' (documented/verified) and that a conditions check is part of the operation, which is useful context, but it never states what the calculation returns or how the trade-off is expressed.

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 sentence with a bilingual gloss, front-loading the core operation before the explanatory aside. It is efficient, though the hyphenated aside is doing work that a clearer statement of the decision rule could have done.

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?

Five required numeric parameters, no output schema, and no annotations about results mean the description should explain the shape of the answer or the decision it produces. It does not, leaving the agent to guess whether the tool returns a boolean verdict, a net saving, or a recommendation.

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% and all five parameters carry their own German descriptions with bounds, so the schema does the heavy lifting. The description adds no meaning beyond that — no clarification of how sollkorb_eur and zusatz_eur combine or why bedingungen_geprueft must hold.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an operation (offsetting a documented discount against unplanned cart value) and the English gloss clarifies it is a cost/benefit test of a coupon. However, the German phrasing is dense and compound, and it never distinguishes this tool from any sibling such as angebote_gesamtpreis_vergleichen or angebot_lagerstatus_zitieren, so an agent must infer the boundary itself.

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 or when-not-to-use guidance and no named alternative. The clause 'items you would not otherwise buy' hints at the scenario, but the agent is left to decide on its own whether to reach for this tool or the related price-comparison sibling.

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