Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

pallet_fitting_calculator

Read-onlyIdempotent

Calculate how many identical boxes fit onto a pallet by optimizing box orientation and stacking within height and weight limits.

Instructions

Calculate how many identical boxes fit on a pallet: boxes per layer (trying 90-degree rotation when allowed), layer count within the max height, totals, volume utilisation and weight capping.

Behavior: deterministic geometric packing of one box size in aligned rows and columns — it does not model interlocked or mixed-orientation patterns; weight_limited reports when max_payload_kg caps the count below the geometric fit; pallet_deck_height_cm defaults to 15. Missing or non-positive dimensions error naming the parameter. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits.

Returns: boxes_per_layer, layers, total_boxes, orientation, boxes_per_row/col, usable_height_cm, utilisation_percent, total_box_volume_cbm, wasted_space_cbm and the weight fields under result, plus confidence, _source and citation (the FreightUtils v1 response envelope).

Limitations: a theoretical best-effort fit — real stacking obeys carton strength, overhang and load-stability rules it does not model.

Related: ldm_calculator (pallets into trailer length), vehicle_lookup (pallet capacity per vehicle), container_lookup (pallets into containers).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
box_width_cmYesBox width in cm.
box_height_cmYesBox height in cm.
box_length_cmYesBox length in cm.
box_weight_kgNoWeight per box in kg — enables the weight-capping check.
allow_rotationNoTry 90-degree box rotation for the best layer fit. Default: true.
max_payload_kgNoMaximum pallet payload in kg. Example: 1000.
pallet_width_cmYesPallet width in cm. Example: 80 (euro pallet).
pallet_length_cmYesPallet length in cm. Example: 120 (euro pallet).
pallet_max_height_cmYesMaximum stack height in cm INCLUDING the pallet deck. Example: 180.
pallet_deck_height_cmNoPallet deck height in cm. Default: 15.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
resultYes
_sourceYes
citationYes
validityNo
warningsNo
confidenceYes
blocking_errorsNo
envelope_versionYes
normalized_inputNo
Behavior5/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint. Description adds deterministic geometric packing details, 90-degree rotation behavior, weight cap reporting (weight_limited field), default pallet_deck_height_cm, and rate-limit behavior with retry instructions. No contradictions.

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?

Description is well-structured with a summary first sentence, then separate sections for behavior, return values, limitations, and related tools. Slightly verbose but every sentence adds value. Could be tightened slightly, but overall effective.

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 10 parameters, output schema existence, and complexity of pallet fitting, the description covers behavior, limitations, return format (enumerates fields under result), rate limits, and related tools. No gaps for a read-only calculator tool.

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?

Input schema has 100% coverage with parameter descriptions. Description adds context: defaults (allow_rotation true, pallet_deck_height_cm 15), unit clarification (cm), and error handling for missing/non-positive dimensions. Enhances understanding beyond schema.

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?

Description clearly states the tool calculates how many identical boxes fit on a pallet, listing specific outputs like boxes per layer, totals, volume utilisation, and weight capping. It distinguishes from sibling tools by mentioning related calculators (ldm_calculator, vehicle_lookup, container_lookup) and specifying the scope (one box size, aligned rows and columns).

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?

Provides explicit context: when to use (one box size, geometric packing), what it does not model (interlocked patterns, real stacking constraints), and alternatives (ldm_calculator for pallets into trailer, etc.). Also explains rate limits and error handling (429 response with retry fields).

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/SoapyRED/freightutils-mcp'

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