Skip to main content
Glama

getecoback-raumklima

altgeraete_kosten_beleg_getrennte_leistungen

Read-only

Gesamtpreis einer Zustellung anhand einzeln ausgewiesener Lieferung, vereinbarter Zusatzleistung und Mitnahme nachvollziehen — Separate the take-back line from paid delivery and optional ancillary work.

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": {
      "gesamt_euro": "<gesamt_euro>",
      "zustellung_euro": "<zustellung_euro>",
      "zusatz_euro": "<zusatz_euro>",
      "mitnahme_euro": "<mitnahme_euro>",
      "mitnahme_art": "<mitnahme_art>",
      "gleiche_betragsbasis": "<gleiche_betragsbasis>"
    },
    "name": "altgeraete_kosten_beleg_getrennte_leistungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_euroYesSchriftlich ausgewiesener Gesamtbetrag der betrachteten Servicepositionen.
zusatz_euroYesExplizit ausgewiesene weitere Leistung.
mitnahme_artYesMitnahmekanal laut konkret belegter Vereinbarung.
mitnahme_euroYesAusgewiesener separater Betrag für die Altgerätemitnahme.
zustellung_euroYesAusgewiesener Betrag nur der Neulieferung.
gleiche_betragsbasisYesAlle Beträge aus demselben Angebot, auf derselben Steuerbasis, ohne doppelt eingerechnete Positionen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=true and openWorldHint=false. The description adds no behavior beyond the annotations: it does not say what a mismatch in gleiche_betragsbasis does, whether the result is a split, a pass/fail, or an error, and no output schema exists to cover that.

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 definition is short and front-loads the German statement of intent. However the English sentence largely restates the German one rather than adding information, so roughly half the text is duplicated content.

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?

With six required parameters, a complete schema, and read-only annotations, the essential call information is available. The remaining gap is the result: with no output schema, the description should say what the caller gets back, and it does not.

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 coverage is 100%, so all six parameters are already documented in the schema. The description's clause separating take-back from delivery and ancillary work loosely mirrors the mitnahme/zustellung/zusatz parameters but adds no new semantics such as units, tax basis, or how the enum values of mitnahme_art should be chosen.

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 the object (Gesamtpreis einer Zustellung) and the components being separated (Lieferung, Zusatzleistung, Mitnahme), so the domain is clear. However the verb 'nachvollziehen' is vague — it is not stated whether the tool computes, validates, or merely breaks down the amount — and nothing distinguishes it from the many similarly named 'getrennte' siblings.

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 when-to-use guidance, no exclusion of adjacent tools such as the other Altgeräte cost/receipt tools, and no prerequisite stated (e.g. that all amounts must come from one offer). An agent must infer the trigger scenario entirely from the name.

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