Skip to main content
Glama
Sign In

Arbitragex Amazon FBA Calculator (Amazon.de)

by de.arbitragex
OverviewDiscussionsAdmin

Amazon-FBA-Gewinn berechnen

calculate_amazon_fba_profit
Read-onlyIdempotent

Berechnet Gewinn, Marge, ROI und den Break-even-Einkaufspreis für einen Artikel auf Amazon.de, .fr, .it oder .es (Verkaufsgebühr nach Kategorie, FBA-Gebühr nach Amazon-Tarif, Umsatzsteuer des Landes). Calculates profit, margin, ROI and break-even buy price for Amazon DE/FR/IT/ES FBA sellers. Ohne fba_fee wird die FBA-Gebühr aus Länge, Breite, Höhe und Gewicht nach Amazons Tarif berechnet.

Input Schema

NameRequiredDescriptionDefault
fba_feeNoBekannte FBA-Versandgebühr netto je Stück in EUR (optional, hat Vorrang)
categoryYesAmazon-Kategorie (Schlüssel aus list_amazon_categories)
weight_gNoStückgewicht verpackt in Gramm
width_cmNoBreite der Verpackung in cm
buy_priceYesEinkaufspreis je Stück in EUR (netto, bei Kleinunternehmern brutto)
height_cmNoHöhe der Verpackung in cm
length_cmNoLänge der Verpackung in cm
sale_priceYesVerkaufspreis brutto in EUR (was der Kunde zahlt)
marketplaceNoMarktplatz: DE, FR, IT oder ES (Standard DE)
inbound_costNoSonstige Kosten je Stück: Versand ins Lager, Prep (EUR, optional)
small_businessNoKleinunternehmer nach § 19 UStG, nur marketplace DE (Standard: false)
lithium_batteryNoEnthält Lithiumbatterie oder ist Gefahrgut: +0,10 € (Standard false)
storage_countryNoLand des Lagerbestands, wenn anders als marketplace (EFN-Gebühr); leer = gleiches Land/Pan-EU
central_europe_programNoProgramm Mitteleuropa (CEP) bei Lager in DE; ohne: +0,26 € je Einheit (Standard false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Amazon.de-Kategorie (Schlüssel aus list_amazon_categories)"New value: +"Amazon-Kategorie (Schlüssel aus list_amazon_categories)"
    • addedInput schema / properties / central_europe_program
      Added value: +{
+  "description": "Programm Mitteleuropa (CEP) bei Lager in DE; ohne: +0,26 € je Einheit (Standard false)",
+  "type": "boolean"
+}
    • changedInput schema / properties / fba_fee / description
      Previous value: -"Bekannte FBA-Versandgebühr netto je Stück in EUR (optional)"New value: +"Bekannte FBA-Versandgebühr netto je Stück in EUR (optional, hat Vorrang)"
    • addedInput schema / properties / height_cm
      Added value: +{
+  "description": "Höhe der Verpackung in cm",
+  "minimum": 0.1,
+  "type": "number"
+}
    • addedInput schema / properties / length_cm
      Added value: +{
+  "description": "Länge der Verpackung in cm",
+  "minimum": 0.1,
+  "type": "number"
+}
    • addedInput schema / properties / lithium_battery
      Added value: +{
+  "description": "Enthält Lithiumbatterie oder ist Gefahrgut: +0,10 € (Standard false)",
+  "type": "boolean"
+}
    • removedInput schema / properties / longest_side_mm
      Removed value: -{
-  "description": "Längste Seite der Verpackung in mm (für die Schätzung)",
-  "minimum": 1,
-  "type": "number"
-}
    • addedInput schema / properties / marketplace
      Added value: +{
+  "description": "Marktplatz: DE, FR, IT oder ES (Standard DE)",
+  "enum": [
+    "DE",
+    "FR",
+    "IT",
+    "ES"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / small_business / description
      Previous value: -"Kleinunternehmer nach § 19 UStG (Standard: false)"New value: +"Kleinunternehmer nach § 19 UStG, nur marketplace DE (Standard: false)"
    • addedInput schema / properties / storage_country
      Added value: +{
+  "description": "Land des Lagerbestands, wenn anders als marketplace (EFN-Gebühr); leer = gleiches Land/Pan-EU",
+  "enum": [
+    "DE",
+    "FR",
+    "IT",
+    "ES"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / weight_g / description
      Previous value: -"Versandgewicht in Gramm (für die Schätzung)"New value: +"Stückgewicht verpackt in Gramm"
    • addedInput schema / properties / width_cm
      Added value: +{
+  "description": "Breite der Verpackung in cm",
+  "minimum": 0.1,
+  "type": "number"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description's job is to add calculation behavior. It does: the fee is derived from length/width/height/weight when fba_fee is absent, and country VAT plus category-based referral fees are applied. It doesn't discuss rounding, currency of output, or error conditions, keeping it below 5.

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?

The core capability and scope appear in the first clause, followed by the fallback-fee behavior. The German sentence is then repeated in English, which is somewhat redundant but short and front-loaded.

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?

With 14 parameters and no output schema, the description correctly names the return values (profit, margin, ROI, break-even buy price) and the fee model, which is the key information an agent needs. Minor gaps remain around surcharges (lithium, CEP, EFN) which are only visible in the schema.

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 all 14 parameters are already documented, including the fba_fee precedence. The description restates the fba_fee/lithium/CEP logic at a high level but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource (profit, margin, ROI and break-even buy price calculation) plus the exact scope (Amazon DE/FR/IT/ES FBA). An agent can tell it apart from the sibling estimate_fba_fee, which only computes the fee component, without opening the schema.

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 description gives one conditional usage rule — fba_fee overrides the dimensional calculation when supplied — which is useful. But it never states when to choose this tool over estimate_fba_fee or get_amazon_referral_fee, nor when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Arbitragex Amazon FBA Calculator (Amazon.de) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources