FreeDailyPro Tools

business_marketplace_fee

Read-onlyIdempotent

Marketplace fee calculator

Input Schema

Name	Required	Description
`cost`	No	What the item costs you. With it the response adds a 'profit' object (profit if kept, returns, margin, ROI, break-even price).
`price`	Yes
`adCost`	No	Ad or acquisition cost per order.
`feePct`	No	Marketplace fee in percent. Required unless compare is sent.
`compare`	No	2 to 4 of Amazon, Etsy, eBay, Walmart, Mercari, TikTok Shop, Shopify. Needs cost. Returns 'comparison': every fee line, payout, profit, margin, ROI and break-even price per marketplace, with the date each preset's rates were verified.
`fixedFee`	No
`returnPct`	No	Share of orders returned, in percent. Default 0 (the website form pre-fills 5).
`fulfilment`	No	Fulfilment fee per unit, e.g. Amazon FBA (in compare it is charged to Amazon only).
`paymentPct`	No	Separate payment-processing fee in percent (0 where the marketplace fee includes it).
`paymentFixed`	No
`shippingCost`	No	What you pay the carrier to send one order. Default 0 (the website form pre-fills 4.50).
`feeOnShipping`	No	Whether the percentage fee also applies to shipping charged. Default true.
`offsiteAdsPct`	No	Compare only: Etsy Offsite Ads fee on the Etsy column, 15% or 12% (capped at $100 per order). Default 0.
`returnPostage`	No	Postage lost on a return. Default 0 (the website form pre-fills 4.50).
`unsellablePct`	No
`ordersPerMonth`	No	Adds the expected profit for a month of that many orders.
`shippingCharged`	No	Shipping the buyer pays on top of price.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 1, 2026

addedInput schema / properties / returnPct / description

Added value: +"Share of orders returned, in percent. Default 0 (the website form pre-fills 5)."

addedInput schema / properties / returnPostage / description

Added value: +"Postage lost on a return. Default 0 (the website form pre-fills 4.50)."

changedInput schema / properties / shippingCost / description

Previous value: -"What you pay the carrier to send one order."New value: +"What you pay the carrier to send one order. Default 0 (the website form pre-fills 4.50)."

Changed16 schema fields changedNov 1, 2026

addedInput schema / properties / adCost

Added value: +{
+  "description": "Ad or acquisition cost per order.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / compare

Added value: +{
+  "description": "2 to 4 of Amazon, Etsy, eBay, Walmart, Mercari, TikTok Shop, Shopify. Needs cost. Returns 'comparison': every fee line, payout, profit, margin, ROI and break-even price per marketplace, with the date each preset's rates were verified.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 4,
+  "minItems": 2,
+  "type": "array"
+}

addedInput schema / properties / cost

Added value: +{
+  "description": "What the item costs you. With it the response adds a 'profit' object (profit if kept, returns, margin, ROI, break-even price).",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / feeOnShipping

Added value: +{
+  "description": "Whether the percentage fee also applies to shipping charged. Default true.",
+  "type": "boolean"
+}

addedInput schema / properties / feePct / description

Added value: +"Marketplace fee in percent. Required unless compare is sent."

addedInput schema / properties / fulfilment

Added value: +{
+  "description": "Fulfilment fee per unit, e.g. Amazon FBA (in compare it is charged to Amazon only).",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / offsiteAdsPct

Added value: +{
+  "description": "Compare only: Etsy Offsite Ads fee on the Etsy column, 15% or 12% (capped at $100 per order). Default 0.",
+  "enum": [
+    0,
+    12,
+    15
+  ],
+  "type": "number"
+}

addedInput schema / properties / ordersPerMonth

Added value: +{
+  "description": "Adds the expected profit for a month of that many orders.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / paymentFixed

Added value: +{
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / paymentPct

Added value: +{
+  "description": "Separate payment-processing fee in percent (0 where the marketplace fee includes it).",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / returnPct

Added value: +{
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / returnPostage

Added value: +{
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / shippingCharged

Added value: +{
+  "description": "Shipping the buyer pays on top of price.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / shippingCost

Added value: +{
+  "description": "What you pay the carrier to send one order.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / unsellablePct

Added value: +{
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}

changedInput schema / required

Previous value: -[
-  "price",
-  "feePct"
-]New value: +[
+  "price"
+]

Changed3 schema fields changedNov 1, 2026
- addedInput schema / properties / feePct / minimum
```
Added value: +0
```
- addedInput schema / properties / fixedFee / minimum
```
Added value: +0
```
- addedInput schema / properties / price / minimum
```
Added value: +0
```
First observedOct 23, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations already declare a safe, read-only, idempotent, closed-world computation, so the safety profile is covered. The description adds nothing on top: it does not disclose that compare requires a cost, that feePct is required unless compare is supplied, that preset marketplace rates carry verification dates, or what the response shape is.

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?

Three words plus a noun phrase — there is no bloat or burying of key information. The brevity is a symptom of under-specification rather than tight editing, but the dimension rewards zero waste and the phrase is front-loaded.

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

Completeness2/5

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

For a 17-parameter tool with conditional requirements (feePct required unless compare; compare requires cost) and no output schema, the description covers none of it. An agent calling with only the required price could hit a validation failure it had no way to anticipate from the description.

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 76%, comfortably in the high band, so the schema already carries most parameter meaning (cost's profit object, compare's 2-4 marketplace strings, default values for returnPct/shippingCost/feeOnShipping). The description contributes no parameter guidance at all, which is acceptable only because the schema does the work.

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

Purpose2/5

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

"Marketplace fee calculator" restates the tool name (business_marketplace_fee) and title almost verbatim, adding no verb/resource specificity. It also fails to distinguish this tool from siblings such as business_product_margin, business_profit_margin and business_break_even, which plausibly overlap in subject matter.

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?

The description gives no when-to-use guidance, no mention of the two distinct modes (a single fee via feePct vs. a multi-marketplace comparison via compare), and no pointer to the neighbouring margin/profit calculators. Nothing steers the agent between this tool and its siblings.

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

All FreeDailyPro Tools tools Inspect

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

Need Help?