Skip to main content
Glama

palletdimensions.com freight reference

Freight class from size and weight

freight_class
Read-onlyIdempotent

Freight class for one LTL handling unit from its size and weight, under the NMFC 13-sub density scale (effective July 19, 2025). weight is the weight of ONE piece, not the total; pieces (default 1) multiplies the cube and the weight. Dimensions default to inches and weight to pounds; set dimUnit to cm and/or weightUnit to kg for metric. roundUp (default false, as the calculator) rounds each side up to the next whole inch when true.

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>",
      "weight": "<weight>"
    },
    "name": "freight_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYesWidth of one handling unit, in dimUnit (same range as length)
heightYesHeight of one handling unit, pallet included, in dimUnit (same range as length)
lengthYesLength of one handling unit, pallet included, at its greatest point, in dimUnit: 1–1000 in or 2.54–2540 cm
piecesNoIdentical pieces in the handling unit
weightYesWeight of ONE piece, in weightUnit (per piece, not the total): 0.1–100000 lb
dimUnitNoin
roundUpNoRound each side up to the next whole inch
weightUnitNolb

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds the governing scale and its effective date plus the rounding rule, which is genuine extra context. It stops short of saying what the call returns (e.g. the class value or density band), a notable gap for a pure-computation tool with no output schema.

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?

A single dense paragraph with no filler: scope, rule-set version, per-piece warning, pieces multiplication, unit defaults and rounding each appear once and in a sensible order. Nothing is repeated from the name or title.

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 an 8-parameter, no-output-schema computation tool, the description covers the units, per-piece semantics, multiplier behavior and rounding mode an agent needs to call it correctly. The only omission is what the result looks like, which for a calculation tool is a modest but real gap.

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?

Adds real meaning beyond the 75%-covered schema: 'pieces' multiplies BOTH the cube and the weight, and roundUp mirrors the calculator default of false, neither of which the schema states. Unit defaults and metric switching are restated rather than extended, but the multiplicative semantics are a genuine clarification.

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?

States a specific verb and resource ('Freight class for one LTL handling unit from its size and weight') and pins the exact rule set ('NMFC 13-sub density scale, effective July 19, 2025'). An agent can immediately distinguish this from siblings like calculate_dim_weight or calculate_cube, which compute different quantities.

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?

Scopes usage tightly by stating it applies to ONE LTL handling unit and clarifying that weight is per piece, not total, which prevents the most common misuse. It gives no explicit 'use X instead when...' routing to siblings, but the scope constraint is clear enough for correct selection.

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