Skip to main content
Glama

load_plan

Compute optimal container loading: determine how many cartons fit by volume and weight, identify the binding constraint, and compare container types. Get overweight warnings and container mix recommendations.

Instructions

Optimize how a product LOADS into a container — the stowage/cube-and-weight question every importer faces. Give the CARTON dimensions (cm) and gross weight (kg) and optionally a target quantity, and it computes: how many units fit BY VOLUME and BY WEIGHT and which constraint BINDS FIRST (the crux — dense cargo like tiles/stone tops out by WEIGHT at low cube, while light cargo like apparel/foam fills the CUBE with payload to spare); the utilization on BOTH axes (% volume AND % payload) so you see the wasted constraint; the 40HC-vs-2×20DV head-to-head for the cargo's density (two 20ft give ~2× the payload for ~the same cube — the right answer for heavy cargo, which a naïve volume-only divide gets wrong); an OVERWEIGHT warning when a box that's 'full' by cube would be ILLEGAL to truck because the destination ROAD/axle weight limit (e.g. US ~38-44k lb cargo on a standard chassis) is far below the ISO 26.7t container plate; and a recommended container MIX for a target quantity with the last box right-sized. Uses real interior dimensions and max payloads of 20DV/40DV/40HC (and reefers) plus per-country road weight caps. Indicative stowage PLANNING (practical-cube loadability, not 3D bin-packing), not a load-securing certification (regla 7). PREMIUM: x402 (USDC on Base) or a prepaid key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
length_cmYesCarton length in cm. REQUIRED.
width_cmYesCarton width in cm. REQUIRED.
height_cmYesCarton height in cm. REQUIRED.
weight_kgYesGross weight per carton in kg. REQUIRED — it drives the weight-binding & overweight logic.
units_per_cartonNoUnits (pieces) per carton, for unit-level totals. Optional; default 1.
reeferNoEvaluate reefer containers (20RF/40RF) instead of dry. Optional.
destination_countryNoDestination ISO-2 country (e.g. 'US', 'DE') → enables the road-weight overweight check. Optional.
heavy_chassisNoUse the heavy/tri-axle road limit instead of the standard chassis cap. Optional.
target_cartonsNoTotal cartons to ship → produces a container MIX. Optional.
target_unitsNoTotal units to ship (converted via units_per_carton) → produces a container mix. Optional.
Behavior5/5

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

With no annotations provided, the description fully discloses the tool's behavior: it computes binding constraints, utilization, container comparisons, overweight warnings, and container mix. It explains limitations (indicative stowage planning, not 3D bin-packing) and mentions premium cost. This provides complete transparency for safe and correct usage.

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 long but every sentence adds unique value. It is front-loaded with the purpose and structured logically: inputs, computations, outputs, and caveats. Despite its length, there is no redundancy, and the information density is high for a complex tool.

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?

Given the tool's complexity (10 parameters, no output schema), the description provides comprehensive coverage of expected outputs, edge cases (dense vs light cargo, overweight warnings), and container mix logic. It even includes pricing details. All essential aspects are addressed, making the tool self-contained.

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?

The input schema has 100% description coverage, but the description adds significant value beyond parameter names and types. For example, it explains that weight_kg drives weight-binding and overweight logic, and describes how optional parameters like target_cartons or destination_country affect outcomes. This provides essential context for parameter usage.

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's purpose: optimizing container loading for stowage and cube/weight constraints. It specifies inputs (carton dimensions and weight) and outputs (units fit, binding constraint, utilization, container comparison, overweight warning, mix recommendation). It distinguishes itself from potential alternatives like pallet planning or load-securing certification.

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 explains when to use (for importer's stowage/cube-and-weight questions) and provides examples (dense cargo vs light cargo). It explicitly states what it is not (load-securing certification). However, it does not directly compare to sibling tools like pallet_plan or cold_chain, which would further clarify when to choose this tool over others.

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