container-loading

plan_load

Compute a 3D load plan for cargo into a container or truck: containers used, utilization (volume & payload %), centre of gravity, crush-protection violations, and a securing checklist (round cargo that rolls, soft cargo that slumps). Cargo type drives realism — drums/pipes hex-nest, big bags/sacks load on top and are never crushed. Omit equipmentCode to auto right-size to the cheapest container that fits. A real API key runs the production PackingSolver optimizer; the public demo key uses the offline preview packer.

Input Schema

Name	Required	Description	Default
`vgm`	No	SOLAS Verified Gross Mass declaration (else a tare+cargo estimate is reported)
`mode`	No	Transport mode — scopes auto right-size to usable equipment (sea→containers, road→trucks, air→ULDs). Ignored when equipmentCode is given.	sea
`items`	Yes	Cargo lines to load
`topUp`	No	Also return `topUp`: for each cargo line, how many MORE units still fit in the same containers with every unit placed and the load still ready (e.g. "+6 of SKU A, fill 82%"). Takes longer, since it re-plans the load per line.
`freight`	No	Freight cost per unit: split the ocean freight for this load (rate per container x containers used) across the cargo lines, per line and per unit, so it can go into product cost. Uses the indicative market rate for the lane (20GP/40GP/40HC, real API key) or your ratePerContainer. Indicative, not a quote. No rate = freight.available false with a reason.
`massLimits`	No	Australian mass tier (default general). hml = HVNL Higher Mass Limits for AU (tri-axle 22.5 t, 6-axle combination 45.5 t; needs an HML route, road-friendly suspension and mass accreditation) or the NT road-friendly-suspension limits for AU-NT. Ignored elsewhere.
`jurisdiction`	No	Road jurisdiction for the axle / gross-weight compliance check (default EU). Set CN for China GB 1589 drayage limits, AU for Australian HVNL general mass limits (NSW, Vic, Qld, SA, Tas, ACT), AU-WA for Western Australia, AU-NT for the Northern Territory. Australian jurisdictions also secure to the HVNL Sch 7 loading performance standards.
`vesselMotion`	No	IMO CSS Annex 13 vessel motion + stowage position. When set, the sea leg uses the position-dependent DYNAMIC acceleration field (a container on deck forward sees a far harsher case than one low amidships) instead of the flat sea-area coefficient.
`equipmentCode`	No	Equipment code, e.g. 40HC (see list_equipment). Omit to auto right-size.
`sequenceStops`	No	Delivery-stop sequencing: with ≥2 distinct deliveryStop values, zone the load nose→doors in reverse delivery order.
`vehicleTareKg`	No	Your road vehicle tare in kg (container: prime mover + chassis/skeletal; truck: the truck). Replaces the nominal tare in the gross check (AU default 14,100 kg, elsewhere 11,600 kg for a container combination).
`complyingSteerAxle`	No	AU only: the prime mover is an HVNL complying steer axle vehicle (6.5 t steer, 44 t combination). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 30, 2026

addedInput schema / properties / complyingSteerAxle

Added value: +{
+  "description": "AU only: the prime mover is an HVNL complying steer axle vehicle (6.5 t steer, 44 t combination). Default false.",
+  "type": "boolean"
+}

addedInput schema / properties / freight

Added value: +{
+  "description": "Freight cost per unit: split the ocean freight for this load (rate per container x containers used) across the cargo lines, per line and per unit, so it can go into product cost. Uses the indicative market rate for the lane (20GP/40GP/40HC, real API key) or your ratePerContainer. Indicative, not a quote. No rate = freight.available false with a reason.",
+  "properties": {
+    "basis": {
+      "description": "Split by cargo volume (default), weight, or chargeable (the larger of the two shares per line).",
+      "enum": [
+        "volume",
+        "weight",
+        "chargeable"
+      ],
+      "type": "string"
+    },
+    "currency": {
+      "description": "ISO 4217 code. Labels ratePerContainer (default USD); with a market rate it must match the lane currency (no conversion).",
+      "type": "string"
+    },
+    "destination": {
+      "description": "Port of discharge, UN/LOCODE (e.g. AUMEL). Needed for a market rate.",
+      "type": "string"
+    },
+    "origin": {
+      "description": "Port of loading, UN/LOCODE (e.g. CNSHA). Needed for a market rate.",
+      "type": "string"
+    },
+    "ratePerContainer": {
+      "description": "Your own rate per container. When given, no market rate is looked up.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / jurisdiction / description

Previous value: -"Road jurisdiction for the axle / gross-weight compliance check (default EU). Set CN for China GB 1589 drayage limits."New value: +"Road jurisdiction for the axle / gross-weight compliance check (default EU). Set CN for China GB 1589 drayage limits, AU for Australian HVNL general mass limits (NSW, Vic, Qld, SA, Tas, ACT), AU-WA for Western Australia, AU-NT for the Northern Territory. Australian jurisdictions also secure to the HVNL Sch 7 loading performance standards."

changedInput schema / properties / jurisdiction / enum

Previous value: -[
-  "EU",
-  "US",
-  "CN"
-]New value: +[
+  "EU",
+  "US",
+  "CN",
+  "AU",
+  "AU-WA",
+  "AU-NT"
+]

addedInput schema / properties / massLimits

Added value: +{
+  "description": "Australian mass tier (default general). hml = HVNL Higher Mass Limits for AU (tri-axle 22.5 t, 6-axle combination 45.5 t; needs an HML route, road-friendly suspension and mass accreditation) or the NT road-friendly-suspension limits for AU-NT. Ignored elsewhere.",
+  "enum": [
+    "general",
+    "hml"
+  ],
+  "type": "string"
+}

addedInput schema / properties / topUp

Added value: +{
+  "description": "Also return `topUp`: for each cargo line, how many MORE units still fit in the same containers with every unit placed and the load still ready (e.g. \"+6 of SKU A, fill 82%\"). Takes longer, since it re-plans the load per line.",
+  "type": "boolean"
+}

addedInput schema / properties / vehicleTareKg

Added value: +{
+  "description": "Your road vehicle tare in kg (container: prime mover + chassis/skeletal; truck: the truck). Replaces the nominal tare in the gross check (AU default 14,100 kg, elsewhere 11,600 kg for a container combination).",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

Changed14 schema fields changedAug 4, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / items / items / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / items / items / properties / compatibilityGroup

Added value: +{
+  "description": "Class-1 explosives compatibility group (A–S).",
+  "type": "string"
+}

addedInput schema / properties / items / items / properties / deliveryStop / maximum
```
Added value: +9007199254740991
```

addedInput schema / properties / items / items / properties / limitedQuantity

Added value: +{
+  "description": "Shipped as a limited quantity (IMDG 3.4) — exempt from most segregation except vs class 1/7.",
+  "type": "boolean"
+}

addedInput schema / properties / items / items / properties / marinePollutant

Added value: +{
+  "description": "Marine pollutant (IMDG 2.10 / MARPOL Annex III). Derived from the DGL.",
+  "type": "boolean"
+}

addedInput schema / properties / items / items / properties / packingGroup

Added value: +{
+  "description": "IMDG packing group. Derived from the UN number when unNumber is set.",
+  "enum": [
+    "I",
+    "II",
+    "III"
+  ],
+  "type": "string"
+}

addedInput schema / properties / items / items / properties / quantity / maximum
```
Added value: +9007199254740991
```

addedInput schema / properties / items / items / properties / segregateFromGroups

Added value: +{
+  "description": "IMDG segregation groups to keep this substance away from (its DGL column-16b provisions).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / segregationGroups

Added value: +{
+  "description": "IMDG 2.7.2.5 segregation groups this substance belongs to.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / subsidiaryHazards

Added value: +{
+  "description": "IMDG subsidiary hazard classes, e.g. [\"6.1\", \"8\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / items / items / properties / unNumber

Added value: +{
+  "description": "UN number, e.g. \"UN1263\" or \"1263\". When set, the engine DERIVES the IMDG class, packing group, subsidiary risks, marine-pollutant status, segregation groups, stowage category and EmS from the curated Dangerous Goods List — no need to hand-enter each. Explicit DG fields override the derived ones.",
+  "type": "string"
+}

addedInput schema / properties / vesselMotion

Added value: +{
+  "description": "IMO CSS Annex 13 vessel motion + stowage position. When set, the sea leg uses the position-dependent DYNAMIC acceleration field (a container on deck forward sees a far harsher case than one low amidships) instead of the flat sea-area coefficient.",
+  "properties": {
+    "bGmFactor": {
+      "description": "Explicit IMO CSS Annex 13 B/GM correction factor (fallback when bOverGm absent).",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "bOverGm": {
+      "description": "Beam / metacentric-height ratio B/GM; derives the Annex 13 transverse B/GM correction.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "lengthFraction": {
+      "description": "Longitudinal stowage position as a fraction of ship length from the aft perpendicular (0=aft, 1=fore).",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "lengthM": {
+      "description": "Ship length between perpendiculars (m); with speedKn, derives the Annex 13 length/speed correction (50–300 m).",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "lengthSpeedFactor": {
+      "description": "Explicit IMO CSS Annex 13 length/speed correction factor (fallback when lengthM/speedKn absent).",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "speedKn": {
+      "description": "Service speed (kn); pairs with lengthM.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "stowageZone": {
+      "description": "Vertical stowage zone.",
+      "enum": [
+        "onDeckHigh",
+        "onDeckLow",
+        "tweendeck",
+        "lowerHold"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "lengthFraction",
+    "stowageZone"
+  ],
+  "type": "object"
+}

removedInput schema / properties / vgm / additionalProperties
```
Removed value: -false
```

Changed5 schema fields changedJul 4, 2026

addedInput schema / properties / items / items / properties / bulky

Added value: +{
+  "default": false,
+  "description": "Bulky/awkward — never takes a load on top and needs handling clearance",
+  "type": "boolean"
+}

addedInput schema / properties / items / items / properties / deliveryStop

Added value: +{
+  "description": "Multi-drop delivery-stop order (1 = first delivered, loaded last at the doors). ≥2 distinct stops + sequenceStops zones the load nose→doors.",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / items / items / properties / thisSideUp

Added value: +{
+  "default": false,
+  "description": "Must stay upright — restricts the packer to upright orientations",
+  "type": "boolean"
+}

addedInput schema / properties / jurisdiction

Added value: +{
+  "description": "Road jurisdiction for the axle / gross-weight compliance check (default EU). Set CN for China GB 1589 drayage limits.",
+  "enum": [
+    "EU",
+    "US",
+    "CN"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sequenceStops

Added value: +{
+  "default": false,
+  "description": "Delivery-stop sequencing: with ≥2 distinct deliveryStop values, zone the load nose→doors in reverse delivery order.",
+  "type": "boolean"
+}

First observedJun 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations, so the description carries the full burden — and it discloses real behavioral traits: cargo `type` changes packing physics (hex-nesting vs never-crushed top loads), and critically that a real API key runs the production PackingSolver while the demo key silently falls back to an offline preview packer (results differ). It does not mention cost/latency beyond 'takes longer' for topUp, nor limits on item counts.

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?

Front-loaded with the output inventory, then behavioral notes, in roughly five dense sentences with no filler. Slightly overloaded with stacked parentheticals ('drums/pipes hex-nest, big bags/sacks load on top'), but every sentence carries information an agent needs.

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?

For a 12-param, deeply nested tool with no output schema and no annotations, the description covers the return surface (containers, utilization, CoG, violations, checklist) and the two behavioral traps (auto right-size, demo vs production solver). The many domain-specific params (vgm, vesselMotion, freight, massLimits) are left entirely to the schema, which is acceptable given 100% coverage.

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 the schema already documents all 12 parameters including nested vgm/vesselMotion/freight. The description adds only marginal semantics beyond that (the equipmentCode omission behavior and the realism effect of `type`), and says nothing about vgm, jurisdiction, massLimits, or vesselMotion. Baseline 3 applies.

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?

Specific verb+resource ('Compute a 3D load plan for cargo into a container or truck') followed by a concrete enumeration of what the plan contains: containers used, utilization, centre of gravity, crush violations, securing checklist. An agent can distinguish this from export_plan or suggest_containers without opening schemas.

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?

Gives actionable routing guidance for the key parameter choice ('Omit equipmentCode to auto right-size to the cheapest container that fits') and points to list_equipment for codes. It does not state when to prefer this over suggest_containers (pre-flight sizing) or export_plan (downstream paperwork), so no explicit exclusions.

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

All container-loading 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.

plan_load

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources