Skip to main content
Glama

palletdimensions.com freight reference

Pallets that fit in a trailer

pallets_per_trailer
Read-onlyIdempotent

How many pallets fit on the floor of a trailer, loaded straight, turned, as the best mix or as side-by-side pinwheel lanes, and stacked when loadHeight and stackable are given. Choose equipment from list_equipment and pallet from its ids, or give palletLength and palletWidth in inches for a custom size. weight is the weight of ONE pallet in pounds and is checked against the trailer payload.

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": {
      "equipment": "<equipment>"
    },
    "name": "pallets_per_trailer"
  }
}

Input Schema

NameRequiredDescriptionDefault
palletNoPallet id. Ignored when palletLength and palletWidth are given48x40
weightNoWeight of ONE pallet in pounds (0.1–10000)
equipmentYesTrailer id
stackableNoWhether the freight can be double-stacked
loadHeightNoLoaded pallet height in inches (1–144), used when stackable is true
palletWidthNoCustom pallet width, in inches (12–120). Give with palletLength
palletLengthNoCustom pallet length, in inches (12–120). Give with palletWidth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: weight is per-pallet and is validated against the trailer's payload limit, and stacking behavior is conditional on loadHeight plus stackable.

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?

Two sentences, front-loaded with the core question, with no filler. The first sentence is long and comma-heavy, packing four loading modes into one clause, but every element carries information.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it never says — for a multi-mode calculator the agent cannot tell whether the response is one count, per-mode counts, or a per-lane breakdown. Inputs and validation are well covered, but the return side is a 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?

Schema coverage is 100%, so the baseline is 3, but the description adds value the schema does not: it clarifies that weight is the weight of ONE pallet (a common mistake) and that it is checked against payload, and it explains the conditional relationship between stackable and loadHeight and the pallet-versus-custom-dimensions override.

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 opens with a specific verb-plus-resource statement: how many pallets fit on a trailer floor, and enumerates the loading modes (straight, turned, best mix, pinwheel lanes) plus the stacking case. An agent can distinguish this from calculate_ti_hi or calculate_cube without opening any schema.

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-sourcing guidance: pick equipment from list_equipment and a pallet id, or supply palletLength/palletWidth for a custom size, and notes stacking applies only when loadHeight and stackable are given. There is no explicit 'use this instead of X' exclusion, which keeps it short of a 5.

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