Skip to main content
Glama

Manifeste: margin and product verdict

calculate_margin
Read-onlyIdempotent

Manifeste e-commerce margin calculator. From a selling price and a delivered cost, returns a GO / RISKY / NO-GO verdict, what the seller really keeps per sale after VAT, platform fees (TikTok Shop, Amazon, Etsy, eBay, own store/Shopify), affiliate commission, payment fees, returns and social contributions, plus the levers to reach GO (minimum price, maximum cost), break-even ROAS, maximum ad cost per sale, sales needed per month and points to check. Use it whenever someone asks if a product is profitable, what margin or fees they will have, or how to price it.

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>",
      "cost": "<cost>"
    },
    "name": "calculate_margin"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYesDelivered cost per unit: product + packaging + shipping to the customer.
priceYesSelling price paid by the customer, tax included (e.g. 24.90).
channelNoWhere it is sold: tiktok (TikTok Shop), amazon, etsy, ebay, boutique (own store, e.g. Shopify), physique (in person), autre (other).
countryNoStore country: FR, BE, DE, ES, IT, IE, UE (other EU), UK, US, XX (other). Sets currency, VAT and default fees.
languageNoLanguage of the answer (default en).
ships_fromNoWhere parcels ship from (matters for TikTok Shop in the EU).
vat_percentNoVAT rate % (default: standard rate of the country; 0 for VAT exemption).
delivery_daysNoBusiness days from order to delivery (optional, used for the verdict).
stock_quantityNoUnits in the first stock order (default 50).
returns_percentNoReturns provision % (default 5).
samples_percentNoFree samples as % of units sold.
starting_budgetNoStarting budget available for stock, ads and samples: returns the max and suggested number of units (30% kept for ads and surprises).
ad_cost_per_saleNoAverage ad spend per sale.
discount_percentNoPromotion % off the price.
shipping_chargedNoShipping paid by the customer, if any.
fixed_fee_per_orderNoOverride the fixed fee per order.
monthly_fixed_costsNoMonthly fixed costs (tools, subscriptions).
monthly_profit_goalNoMonthly net profit goal (default 1000).
payment_fee_percentNoOverride payment fees %.
platform_fee_percentNoOverride the platform fee %.
affiliate_commission_percentNoAffiliate creator commission % (TikTok Shop default 15).
social_contributions_percentNoSocial contributions and taxes as % of revenue (France micro-entreprise default 12.3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / starting_budget
      Added value: +{
      +  "description": "Starting budget available for stock, ads and samples: returns the max and suggested number of units (30% kept for ads and surprises).",
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, non-destructive and closed-world, which matches a pure calculator, and nothing in the description contradicts that. The description does add useful behavioral context by spelling out the return payload (verdict, retained amount, levers, break-even ROAS, points to check) and the 30%-for-ads budgeting rule, but it omits how defaults are resolved per country or what the response structure looks like. With annotations covering the safety profile, a 3 is appropriate – value is added, but key behavioral detail is still missing.

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?

Three sentences, front-loaded with the identity of the tool, then the output inventory, then the usage trigger. The middle sentence is a dense 60-word enumeration of outputs, which is informative but heavier than needed; the parentheses for platform examples could be trimmed.

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?

For a 22-parameter tool with no output schema, the description carries the burden of explaining return values, and it does so thoroughly by listing the verdict, net-per-sale breakdown, minimum price, maximum cost, break-even ROAS, max ad cost, and monthly sales target. What is missing is any explanation of how the many optional overrides and country defaults interact, which matters given only 2 of 22 parameters are required.

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% and all 22 parameters carry detailed descriptions including defaults and enum meanings, so the schema does the heavy lifting. The description only restates the two required inputs (selling price, delivered cost) and adds nothing about defaults, enum choices, or how overrides interact with country-based fee defaults; the baseline 3 applies.

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

Purpose4/5

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

The description names a specific computation (margin calculation from selling price and delivered cost) and enumerates the concrete outputs: GO/RISKY/NO-GO verdict, net kept per sale, break-even ROAS, minimum price and maximum cost. It is unambiguous about what the tool does, though it never mentions the sibling compare_channels, so an agent gets no explicit routing signal between the two.

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 final sentence gives clear when-to-use triggers: profitability questions, margin/fee questions, and pricing questions. There is no when-not guidance and no reference to an alternative tool, so the agent must infer that compare_channels is for cross-channel comparison rather than single-product verdicts.

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