Skip to main content
Glama

Manifeste: compare sales channels

compare_channels
Read-onlyIdempotent

Compares the same product (price, delivered cost) across TikTok Shop, Amazon, Etsy, eBay and an own online store in one country, with the verdict and net kept per sale on each channel.

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": "compare_channels"
  }
}

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the analytical scope (all channels in one country, verdict plus net kept per sale), which is genuine value. It does not disclose return format, whether results are cached, or how the verdict is computed, so it adds moderate rather than rich behavioral context.

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?

It is a single front-loaded sentence with no filler or repetition, and the key scope constraint (same product, one country) appears early. It is dense with stacked clauses, but every clause carries information.

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 no output schema, the sentence does name the two things returned (the verdict and the net kept per sale on each channel), which is the minimum needed to know what comes back. For a 22-parameter tool it omits that most parameters are optional with defaults and that budget inputs change the return shape, leaving a modest gap. Given annotations cover safety and the schema covers every parameter, the description is close to complete.

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% across all 22 parameters, including defaults, enum meanings and units, so the schema carries the full semantic load. The description contributes no parameter-level meaning beyond what the schema already states (e.g. what the cost figure must include, what country controls). Baseline 3 is appropriate when structured fields do the work.

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 states a specific verb and resource (compares the same product's price and delivered cost) and enumerates the channels and scope (one country), plus the outputs it derives (verdict, net kept per sale). This is far more specific than a restatement of the name. It stops short of naming the sibling calculate_margin or clarifying how it differs from a single-channel margin calculation.

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?

There is no explicit when-to-use or when-not-to-use guidance, and the only sibling, calculate_margin, is never mentioned. An agent must infer from the verb that this is the multi-channel comparison path versus a single-channel margin path. Useful usage context is absent rather than merely sparse.

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