Skip to main content
Glama

Arbitragex Amazon FBA Calculator (Amazon.de)

FBA-Gebühr nach Amazon-Tarif

estimate_fba_fee
Read-onlyIdempotent

FBA-Versandgebühr (netto) je Einheit für Amazon.de, .fr, .it oder .es nach Amazons Tarifübersicht ab 01.07.2026: Größenklasse und Versandgewicht aus den Maßen, Tarif des Landes, Aufschlag (1,5 %, ab 02.11.2026 2 %), Programm Mitteleuropa, EFN, Hochsaison DE, Niedrigpreistarif (dafür sale_price und category angeben). Amazon FBA fulfilment fee for DE/FR/IT/ES from the official rate card.

Input Schema

NameRequiredDescriptionDefault
categoryNoKategorie-Schlüssel (optional)
weight_gYesStückgewicht verpackt in Gramm
width_cmYesBreite der Verpackung in cm
height_cmYesHöhe der Verpackung in cm
length_cmYesLänge der Verpackung in cm
sale_priceNoVerkaufspreis brutto in EUR (optional, für den Niedrigpreistarif)
marketplaceNoMarktplatz: DE, FR, IT oder ES (Standard DE)
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
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Kategorie-Schlüssel (optional)",
      +  "enum": [
      +    "zubehoer-amazon-geraete",
      +    "auto-motorsport",
      +    "baby",
      +    "kinderwagen",
      +    "rucksaecke-handtaschen",
      +    "beauty-drogerie",
      +    "arbeitshandschuhe",
      +    "bier-wein-spirituosen",
      +    "buecher",
      +    "gewerbe-industrie",
      +    "bekleidung",
      +    "elektronik-gewerbe-energie",
      +    "kompakte-elektrogeraete",
      +    "computer",
      +    "elektronik",
      +    "fahrradzubehoer",
      +    "elektronik-zubehoer",
      +    "drucker-scanner-zubehoer",
      +    "brillen",
      +    "augenschutz",
      +    "schuhe",
      +    "elektrogeraete-standard",
      +    "moebel",
      +    "moebelzubehoer",
      +    "lebensmittel",
      +    "handmade",
      +    "haushalt",
      +    "kueche",
      +    "heimtextilien",
      +    "schmuck",
      +    "garten",
      +    "koffer-taschen",
      +    "koffer-zubehoer",
      +    "matratzen",
      +    "musik-video-dvd",
      +    "musikinstrumente",
      +    "buerobedarf",
      +    "verpackung",
      +    "haustierbedarf",
      +    "haustier-kleidung-futter",
      +    "software",
      +    "sport-freizeit",
      +    "reifen",
      +    "werkzeuge-baumarkt",
      +    "tuer-fenster-dusche",
      +    "kleber-kabelbinder",
      +    "spielzeug",
      +    "videospiele",
      +    "konsolen",
      +    "vitamine",
      +    "uhren",
      +    "andere"
      +  ],
      +  "type": "string"
      +}
    • 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"
      +}
    • 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",
      -  "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"
      +}
    • addedInput schema / properties / sale_price
      Added value: +{
      +  "description": "Verkaufspreis brutto in EUR (optional, für den Niedrigpreistarif)",
      +  "minimum": 0.01,
      +  "type": "number"
      +}
    • 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"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"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "longest_side_mm",
      -  "weight_g"
      -]New value: +[
      +  "length_cm",
      +  "width_cm",
      +  "height_cm",
      +  "weight_g"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses the rate-card effective date, country tariffs, surcharge percentages, CEP, EFN, DE high-season treatment, and low-price tariff conditions. These are substantive behavioral details an agent needs to interpret the calculation.

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 description is front-loaded with the fee calculation and appropriately dense for a 10-parameter pricing tool. The single long German sentence is somewhat run-on, but almost every clause conveys relevant rate-card behavior.

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?

The description covers the calculation target, marketplaces, rate period, and major conditional surcharges/programs, which is substantial for a complex fee tool with no output schema. It could be slightly stronger by explicitly stating the returned unit/currency and rounding assumptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful relationships, especially that the low-price tariff requires both sale_price and category, and it contextualizes EFN and CEP inputs beyond the individual schema descriptions.

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?

The description states a specific calculation: net FBA shipping fee per unit for DE/FR/IT/ES based on Amazon's official rate card. It clearly distinguishes this from referral-fee and profit-calculation siblings by focusing narrowly on the FBA fulfilment fee.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when conditional inputs apply, such as sale_price and category for the low-price tariff, CEP, EFN, and DE high season. It does not explicitly name alternatives or say when not to use this versus calculate_amazon_fba_profit, but the usage context is otherwise clear.

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