Skip to main content
Glama

palletdimensions.com freight reference

Dimensional weight of a package

calculate_dim_weight
Read-onlyIdempotent

Dimensional (DIM) weight of one package in pounds and kilograms: length × width × height in inches, rounded as the service rules say, divided by that service divisor. service picks the carrier and rate (default ups-daily): ups-daily = UPS UPS packages, Daily Rates; ups-retail-domestic = UPS UPS domestic packages, Retail Rates; ups-retail-export = UPS UPS export packages, Retail Rates; fedex-packages = FedEx FedEx U.S. and international package services and Express Freight (not International Deferred Freight or One Rate); fedex-intl-deferred = FedEx FedEx International Deferred Freight; fedex-ground-economy = FedEx FedEx Ground Economy at 1 lb or more, including Bound Printed Matter, Media and Returns; usps-priority = USPS USPS Priority Mail, retail, to Zones 1-9. Services whose checked sources state no rounding rule are left unrounded. USPS retail Priority Mail applies dimensional weight only above its volume floor. Give actualWeight to compare it with the dimensional weight; this tool does not work out a charge.

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_dim_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoin
widthYesPackage width, in unit
heightYesPackage height, in unit
lengthYesPackage length, in unit
serviceNoCarrier service idups-daily
actualWeightNoActual weight, in actualWeightUnit. Optional
actualWeightUnitNolb

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 establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower, but the description still adds real behavior: services lacking a documented rounding rule are left unrounded, and USPS retail Priority Mail applies DIM weight only above its volume floor. That is meaningful domain context beyond the annotations.

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?

The purpose and formula are front-loaded, which is good, but the service enumeration is a dense run-on with duplicated tokens ('UPS UPS packages', 'FedEx FedEx U.S.') that hurt readability. A bulleted mapping of service ids would carry the same information more efficiently.

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?

With no output schema, the description correctly states the result is expressed in both pounds and kilograms, and it bounds the tool's scope by excluding charge calculation. It does not state rounding precision of the returned number, which would be the last missing detail for a seven-parameter calculator.

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 71%, and the description compensates by spelling out what each `service` enum value means (carrier, rate type, exclusions such as 'not International Deferred Freight or One Rate') and why `actualWeight` exists. One flaw: it describes dimensions as 'in inches' while the schema permits `unit: cm`, which could mislead.

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 opening sentence gives a specific computation (length × width × height, rounded per service rule, divided by the service divisor) and the output units (pounds and kilograms). This clearly separates it from siblings such as calculate_cube or freight_class, which do not compute DIM weight.

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 states that `service` selects the carrier and rate with a default of ups-daily, and each enum value is explained so the agent knows which one applies. It also bounds the tool's scope: 'Give actualWeight to compare it with the dimensional weight; this tool does not work out a charge.' It does not, however, name a sibling alternative for charge estimation.

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