Skip to main content
Glama

palletdimensions.com freight reference

Cartons per layer and per pallet (Ti × Hi)

calculate_ti_hi
Read-onlyIdempotent

Cartons per layer (Ti), layers per pallet (Hi) and cartons per pallet for one carton size, the load height and the total weight. Ti is the best of an all-one-way pattern, an all-turned pattern and two two-block mixes; the carton height stays vertical. All lengths are in unit (in or cm). Choose pallet from list_equipment ids (default 48x40) or give palletLength and palletWidth. overhang is how far the load may hang past each pallet edge (default 0). Give maxHeight (total load height, pallet included) with deckHeight (the empty pallet height) for Hi; without them only Ti is returned. Neither is assumed: the page offers sourced starting values. Give cartonWeight (and palletWeight) for the total weight. Capacity ratings for a 48 × 40 pallet appear only as a warning.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "length": "<length>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "calculate_ti_hi"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for every lengthin
widthYesCarton width, in unit
heightYesCarton height, in unit. This side stays vertical
lengthYesCarton length, in unit
palletNoPallet id. Ignored when palletLength and palletWidth are given48x40
overhangNoOverhang allowed past each pallet edge, in unit
maxHeightNoGreatest total load height, pallet included, in unit. Give with deckHeight
deckHeightNoHeight of the empty pallet, in unit. Required with maxHeight
weightUnitNolb
palletWidthNoCustom pallet width, in unit. Give with palletLength
cartonWeightNoWeight of one carton, in weightUnit
palletLengthNoCustom pallet length, in unit. Give with palletWidth
palletWeightNoWeight of the empty pallet, in weightUnit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish this as a read-only, idempotent, closed-world calculation, so the description only needs to add conditional-output behavior. It does add some: partial results (Ti only) when heights are omitted, and the fact that capacity ratings surface only as a warning for 48x40. However, the phrase 'the page offers sourced starting values' is confusing and does not describe how the tool itself behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It front-loads the outputs, which is good, but the body is a dense run-on of semicolon-linked clauses mixing algorithm notes, input fallbacks, and warnings. The 'page offers sourced starting values' sentence is a UI reference that does not earn its place in a tool description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with no output schema, the description should identify the returned fields, yet it only says that Ti alone may come back. The input side is well covered and the conditional logic is explained, but an agent still cannot predict the response shape.

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?

With 92% schema description coverage the schema already documents nearly every parameter, so the baseline is a 3. The description adds a little meaning, notably that the unit setting governs every length and that pallet ids take precedence over custom dimensions, but most of its parameter prose restates what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific outputs computed (Ti, Hi, cartons per pallet, load height, total weight) and briefly discloses the packing algorithm (best of one-way, all-turned, and two two-block mixes, with carton height vertical). That is enough to tell it apart from calculate_cube or calculate_dim_weight, though it never explicitly contrasts itself with those siblings.

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?

It gives concrete input-selection guidance: obtain pallet ids from list_equipment or supply palletLength/palletWidth, and it states the condition under which Hi is computed versus Ti-only (maxHeight plus deckHeight present). What is missing is any statement about when to prefer this tool over the other calculation siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources