Manifeste

Manifeste: compare sales channels

compare_channels

Read-only

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.

Input Schema

Name	Required	Description
`cost`	Yes	Delivered cost per unit: product + packaging + shipping to the customer.
`price`	Yes	Selling price paid by the customer, tax included (e.g. 24.90).
`channel`	No	Where it is sold: tiktok (TikTok Shop), amazon, etsy, ebay, boutique (own store, e.g. Shopify), physique (in person), autre (other).
`country`	No	Store country: FR, BE, DE, ES, IT, IE, UE (other EU), UK, US, XX (other). Sets currency, VAT and default fees.
`language`	No	Language of the answer (default en).
`ships_from`	No	Where parcels ship from (matters for TikTok Shop in the EU).
`vat_percent`	No	VAT rate % (default: standard rate of the country; 0 for VAT exemption).
`delivery_days`	No	Business days from order to delivery (optional, used for the verdict).
`stock_quantity`	No	Units in the first stock order (default 50).
`returns_percent`	No	Returns provision % (default 5).
`samples_percent`	No	Free samples as % of units sold.
`ad_cost_per_sale`	No	Average ad spend per sale.
`discount_percent`	No	Promotion % off the price.
`shipping_charged`	No	Shipping paid by the customer, if any.
`fixed_fee_per_order`	No	Override the fixed fee per order.
`monthly_fixed_costs`	No	Monthly fixed costs (tools, subscriptions).
`monthly_profit_goal`	No	Monthly net profit goal (default 1000).
`payment_fee_percent`	No	Override payment fees %.
`platform_fee_percent`	No	Override the platform fee %.
`affiliate_commission_percent`	No	Affiliate creator commission % (TikTok Shop default 15).
`social_contributions_percent`	No	Social contributions and taxes as % of revenue (France micro-entreprise default 12.3).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavioral context by saying the tool produces a verdict and net kept per sale on each channel, though it omits limitations and assumption details that might affect results.

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?

The description is a single front-loaded sentence with no wasted wording. It efficiently names the comparison scope, channels, country constraint, and result shape.

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?

Given the rich 100% schema coverage and read-only annotations, the description provides enough high-level context to understand the tool's purpose and output shape. It is slightly thin for a 21-parameter tool and does not explain how optional assumptions affect the comparison, but the schema fills those gaps.

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%, so all 21 parameters are already documented in the schema. The description mentions key inputs like price, delivered cost, channels, and country, but it does not add meaning beyond what the schema provides.

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: comparing the same product's price and delivered cost across named sales channels in one country. It is clear what the tool does, but it does not explicitly differentiate itself from the sibling tool calculate_margin.

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

Usage Guidelines3/5

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

The description implies the tool is for multi-channel comparison within one country, but it does not state when to use it versus calculate_margin or when it should not be used. Usage is inferable but not explicitly guided.

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

All Manifeste 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?