Skip to main content
Glama

3DPACK.ING — Container & 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.

TDQS

A4.7/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 what the tool returns (containers needed, fullness, non-fitting items, a 3D load plan link) and how the solver behaves regarding stacking constraints. It does not cover errors or failure modes, but for a non-mutating computational tool this is adequate transparency.

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?

Three focused paragraphs with no filler: the main purpose is front-loaded, the volume-estimation alternative is justified in one sentence, and the stability note is specific and actionable. The examples are compact but informative.

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?

For a tool with no output schema and no annotations, the description provides enough: usage context, sample inputs, parameter tradeoffs, and expected outputs. An agent has all the information it needs to call the tool correctly and interpret the response.

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 schema already documents all three parameters. The description adds meaningful value beyond the schema by explaining how to construct prompt examples, clarifying that stability is the one constraint the prompt cannot express, and describing the tradeoff that higher stability fits fewer items.

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 uses a specific verb and resource: 'work out how a shipment fits into shipping containers, trucks or pallets' with a real 3D bin-packing solver. It clearly distinguishes itself from volume estimation, and since there are no sibling tools, it does not need further differentiation.

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?

The description explicitly says 'Use this instead of estimating from volume' and explains why, which is a clear when-to-use and when-not-to-use signal. It also gives concrete input guidance, examples, and highlights the special stability parameter for a specific class of cargo.

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

All 3DPACK.ING — Container & 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

With only one tool, there is no possibility of confusion between tools. The single tool has a clear, unambiguous purpose: it handles the entire shipment packing process.

Naming Consistency5/5

The sole tool name 'pack_shipment' follows the verb_noun pattern, which is clear and consistent. Since there is only one tool, consistency is trivially maintained.

Tool Count3/5

A single tool is on the thin side for a server, but it is a comprehensive all-in-one tool for load planning. While the count feels minimal, it may be acceptable for such a specialized domain.

Completeness5/5

The tool fully covers the shipment packing workflow: it accepts cargo details and constraints, computes the packing, returns container needs, fill levels, and leftovers, and provides an interactive plan. No obvious gaps in the domain.

Resources