Skip to main content
Glama

reverse_logistics

Analyze return, destroy, or liquidate options for goods at destination to maximize recovery, accounting for duty drawback, reverse freight, and storage costs.

Instructions

The reverse flow almost nobody models: goods have to come BACK from the destination market — what do you do with them? Give the lane + how many units + their value + condition (defective / RMA / over-stock / surplus), and it prices the three dispositions per unit and picks the best NET RECOVERY: RETURN (reverse freight ≈1.6× forward + recondition/handling, reclaiming the re-export DUTY DRAWBACK already paid — 99% recovery, but Section-301 duty is carved out), DESTROY in destination (cheap, zero product value, still drawback-eligible) or LIQUIDATE into the destination secondary market (some cash back, no reverse freight, no drawback). It proves the rule: high unit value + recoverable duty + cheap reverse freight → RETURN; reverse freight per unit above the recoverable value → never ship it home (destroy for the drawback, or liquidate locally — whichever nets more). Flags the storage bleed that forces the decision window. Honest (regla 7): INDICATIVE recovery fractions, freight multipliers & handling defaults you should override; drawback eligibility and the §301 carve-out are real but filing-specific — NOT customs/legal advice. PREMIUM: pay per call with x402 (USDC on Base) or a prepaid key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
origin_portYesOrigin port (where the goods would RETURN to). City name, UN/LOCODE, or 'City, Country'.
dest_portYesDestination port (where the goods currently are).
container_typeNoContainer '20ft'/'40ft'/'40HC'. Optional; default '40ft'.
quantity_unitsYesHow many units are coming back. REQUIRED.
unit_value_usdYesPer-unit value (USD). REQUIRED — drives recovery, handling and the decision.
conditionNo'defective' / 'rma' / 'overstock' / 'surplus' — sets recovery & recondition. Optional; default rma.
duty_paid_per_unit_usdNoDuty already paid per unit on the original import (USD) — drives the drawback reclaim. Optional; default 0.
section301_per_unit_usdNoOf that duty, the Section-301 slice per unit (USD) — NOT drawback-eligible. Optional; default 0.
drawback_eligibleNoIs re-export/destruction drawback available to you? Optional; default true.
recondition_hubNoReturn to a reconditioning HUB instead of origin (shorter, cheaper return leg). Optional.
forward_freight_per_unit_usdNoOverride the forward per-unit freight (USD) instead of deriving it from the lane. Optional.
units_per_containerNoUnits per container — to spread container freight over units. Optional.
pending_daysNoDays the goods sit pending a decision (storage bleed). Optional; default 0.
ship_dateNoShip date (YYYY-MM-DD) for the freight anchor. Optional.
Behavior5/5

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

No annotations provided, so description carries full burden. It thoroughly explains the three dispositions, recovery math (freight multipliers, drawback eligibility, Section 301 carve-out), storage bleed, and the indicative nature of outputs. It also notes the tool is not legal advice and mentions premium pricing.

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?

The description is lengthy but well-structured: problem statement, required inputs, logic explanation, honest caveats. Every sentence adds value, though some sections are dense. It front-loads the core purpose and gradually details specifics, making it readable despite length.

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 14 parameters and no output schema, the description covers the tool's functionality comprehensively: storage bleed, drawback rules, freight multipliers, condition defaults. It lacks explicit output field names but the expected result (best disposition and recovery) is clear. For a complex tool, this is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant context: how unit_value_usd drives recovery, duty_paid and section301 affect drawback, condition sets recovery/recondition, and defaults like 'rma' for condition. It explains interactions between parameters and the decision logic, far exceeding mere schema repetition.

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?

The description clearly states the tool evaluates reverse logistics decisions (return, destroy, liquidate) and identifies the best net recovery. It specifies inputs (lane, units, value, condition) and outputs (priced dispositions). The tool is distinct from sibling tools like 'ship_decision' which focuses on forward logistics.

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 description implies when to use: for reverse flow decisions of goods returning from destination. It includes caveats about indicative results and overriding defaults. However, it does not explicitly state when not to use or point to alternative tools, though the unique purpose makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Baneado98/freight-pulse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server