Skip to main content
Glama

3DPACK.ING — Truck Load Planning

by ing.3dpack

Pack a shipment into containers or trucks

pack_shipment

Work out how a shipment fits into shipping containers, trucks or pallets, using a real 3D bin-packing solver. Describe the cargo in plain English -- quantities, dimensions, weights, and any constraints such as fragile, non-tiltable, max stack height or a preferred container type -- and get back which containers are needed, how full each one is, anything that did not fit, and a link to an interactive 3D load plan.

Use this instead of estimating from volume. Volume arithmetic ignores stacking rules, orientation and weight limits, and overstates what fits by a wide margin on real cargo.

For cargo that must not overhang -- drums, glass, anything that must stay level -- set stability. It is the one constraint the prompt cannot express, because it governs how the solver stacks rather than what is being shipped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speedNoHow hard the solver should look for a better arrangement. Omit to let it choose. Use 'fast' for a quick feasibility check, 'thorough' when the packing quality matters.
promptYesThe shipment, in plain English. Include quantities, dimensions with units, and weights if known. Examples: "Pack 50 boxes of 60x40x30 cm into a 20ft container"; "Load 100 fragile items 80x60x40cm, max stack 3, into a 40ft high cube"; "Ship mixed pallets: 10x euro pallets, 15x US pallets, best container mix". Truncated at 4000 characters.
stabilityNoHow much of a box must rest on what is underneath it, as a percentage of its own footprint. Omit for the standard rule of 75, which allows a quarter of a box to overhang and packs the most. Raise it for cargo that must not lean -- drums, glass, anything top-heavy -- and use 100 when every stacked box has to sit fully supported. A higher value is steadier and fits fewer items, so expect more containers or more left over.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses the input format, the kinds of constraints that can be expressed, the expected output (containers needed, fullness, non-fits, 3D plan link), and the important caveat that stability cannot be expressed in the prompt. It does not discuss side effects, authentication, or rate limits, but the computation-like nature is clear.

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 efficient and well-structured: purpose first, then when-to-use reasoning, then the one nuanced parameter. Every sentence contributes useful signal, and it avoids repeating schema definitions.

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 tool with no annotations and no output schema, the description provides a complete mental model: how to describe cargo, what the solver does, what the response contains, and the stability caveat. It could mention speed tradeoffs explicitly, but the schema already documents those, so nothing essential is missing.

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 coverage is 100%, so the baseline is 3, and the description adds meaningful value beyond the schema. It explains why stability is a separate parameter, what the default 75 means, the packing tradeoff of higher values, and gives concrete prompt construction guidance. Speed is only covered by the schema, but the most non-obvious parameter receives strong additional semantics.

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 states a specific verb and resource: 'Work out how a shipment fits into shipping containers, trucks or pallets' using a 3D bin-packing solver. It clearly distinguishes the tool from volume-based estimation, so an agent immediately understands what job it performs.

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?

It explicitly says 'Use this instead of estimating from volume' and explains why volume arithmetic is inadequate. It also gives a concrete usage condition for the stability parameter, making it clear when to adjust it versus leaving it at the default.

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

All 3DPACK.ING — Truck Load Planning toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

There is only one tool, so there is no risk of an agent confusing it with another operation. pack_shipment has a single, clearly defined purpose: generating a 3D load plan for a shipment.

Naming Consistency5/5

The sole tool name, pack_shipment, follows a clean verb_noun pattern. With no other tools present, there are no naming conventions to conflict with it.

Tool Count3/5

One tool is at the thin end of the range, but pack_shipment is a substantial, general-purpose planning entry point rather than a trivial helper. The count feels borderline but not necessarily wrong for a focused single-purpose solver.

Completeness5/5

For the stated domain of truck, container, and pallet load planning, pack_shipment covers the essential workflow: describe cargo and constraints, get a load plan, see fill levels and unfitted items, and access an interactive visualization. There are no obvious dead ends within this single-operation scope.

Resources