Moltline Dropship Economics

Returns Impact

returns_impact

Read-onlyIdempotent

Show what a return rate does to a margin that looked fine. PREMIUM (license).

A 10% return rate does not cost 10% of profit. A returned order gives back the refund, adds inbound shipping, and recovers only the goods, never the advertising that found the buyer. Typical input {"sell_price": 39.99, "unit_profit": 13.23, "unit_cost": 12.4, "return_rate_pct": 8, "restock_pct": 70, "return_shipping": 6} returns {"cost_per_return": 37.31, "effective_profit": 10.25, "profit_lost_pct": 22.56, "break_even_return_rate_pct": 35.46}.

Use when a category's returns are high enough to argue about. Not for the pre-returns margin itself: that is margin_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": ""}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input Schema

Name	Required	Description
`unit_cost`	Yes	What the goods themselves cost you, the only part a restocked unit gives back. Advertising and fees do not return.
`refund_pct`	No	Percentage of the sale price refunded, e.g. 100 for a full refund or 80 when a restocking fee is kept. Default 100.
`sell_price`	Yes	Price the customer paid.
`restock_pct`	No	Percentage of returned units resellable at full price. Default 0, the conservative case.
`unit_profit`	Yes	Profit on one kept sale, from margin_check. May be negative, which the result will make obvious.
`return_rate_pct`	Yes	Percentage of orders returned, e.g. 8.
`return_shipping`	No	What an inbound return costs you. Default 0.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / unit_cost / description

Previous value: -"What the goods themselves cost you — the only part a\nrestocked unit gives back. Advertising and fees do not return."New value: +"What the goods themselves cost you, the only part a\nrestocked unit gives back. Advertising and fees do not return."

First observedAug 20, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description usefully adds that invalid input returns a structured {error} object rather than a protocol error, making the retry model clear. However, it does not add much beyond what the annotations plus output schema already convey, so a 3 is appropriate.

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?

Purpose is front-loaded, followed by a why-it-matters explanation, a concrete example, then usage and error notes. The premium/license tag is placed prominently. Slight verbosity in the middle explanation, but most sentences carry real meaning.

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?

Output schema exists, so return values needn't be spelled out, yet the description still shows a sample result for orientation. Combined with error handling and retry guidance for a 7-param tool, an agent has everything needed to invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description's example input/output pair adds interpretive value by showing how return_shipping and restock_pct combine into cost_per_return and effective_profit, which helps an agent choose realistic values. It stops short of explaining each parameter individually, so it sits just above baseline.

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+resource: shows how a return rate erodes an apparently healthy margin, with worked input/output numbers. It explicitly distinguishes the scope from margin_check ('Not for the pre-returns margin itself'), so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use when a category's returns are high enough to argue about') and names the alternative sibling margin_check plus the condition that selects it. Nothing about when to prefer this tool is left to inference.

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

All Moltline Dropship Economics 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.