Skip to main content
Glama

get_fee_estimate

Read-only

Estimate Amazon fees (referral + FBA + variable closing) and net proceeds for a given selling price, via the official Amazon Product Fees API (getMyFeesEstimate). Pass asin OR sku, the price, currency and fulfillment_channel (FBA default, or FBM). Returns referral_fee, fba_fee, closing_fee, total_fees and net_proceeds (price minus Amazon fees, before your cost of goods). Use it for real margins: margin = net_proceeds - purchase cost. Read-only.

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": {
      "price": "<price>"
    },
    "name": "get_fee_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNoSKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano).
asinNoASIN Amazon di 10 caratteri, es. B08N5WRWNW.
priceYesPrezzo di vendita in valuta del marketplace, es. 19.90.
currencyNoISO code, default EUR
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
fulfillment_channelNoFBA (default) or FBM

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / asin / description
      Added value: +"ASIN Amazon di 10 caratteri, es. B08N5WRWNW."
    • addedInput schema / properties / price / description
      Added value: +"Prezzo di vendita in valuta del marketplace, es. 19.90."
    • addedInput schema / properties / sku / description
      Added value: +"SKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano)."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/destructive, so the trailing 'Read-only' earns no credit. The description does add real behavioral context: the underlying official API, the exact composition of net_proceeds and the important caveat that it excludes cost of goods. It omits operational traits such as rate limits or what happens when the ASIN/SKU is not in the seller catalog.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what is estimated, then the inputs, then the outputs, then the margin formula. Every sentence carries actionable information with no filler, despite being a fairly dense paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, no output schema, and a computational tool, the description compensates well by enumerating the return fields and defining net_proceeds. Nothing an agent needs in order to call it and interpret the result is missing.

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 coverage is 100%, so baseline is 3, but the description adds a constraint the schema does not express: 'Pass asin OR sku' — both are optional in the schema with no oneOf, so this disambiguation is genuinely useful. It also restates the FBA-default fulfillment_channel meaning, which the schema already carries, keeping it below a 5.

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 ('Estimate Amazon fees'), enumerates the exact fee components computed (referral + FBA + variable closing), names the backing API (getMyFeesEstimate), and lists the returned fields. An agent can tell this apart from the pricing siblings (get_my_pricing, get_competitive_pricing) because it is about fee/margin computation rather than price retrieval.

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?

Gives a concrete use case ('Use it for real margins: margin = net_proceeds - purchase cost') that tells the agent when this tool is the right pick, and implicitly excludes it from simple price lookups. It stops short of naming an alternative tool or stating when-not to use it, so it falls short of a 5.

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