Skip to main content
Glama

palletdimensions.com freight reference

Cubic feet and cubic metres of a shipment

calculate_cube
Read-onlyIdempotent

Total volume of up to 20 lines of identical pieces, in cubic feet, cubic metres, cubic inches, cubic yards and litres. Each item has length, width, height in unit (in, ft, yd, mm, cm or m; default in) and quantity (default 1). When every item has a weight, also returns total weight, density in lb/ft³ and kg/m³, and ocean weight/measurement (the larger of m³ and tonnes). weight is per piece unless weightBasis is line. rounding (default exact) can round each side up or to the nearest whole inch first.

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": {
      "items": "<items>"
    },
    "name": "calculate_cube"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
roundingNoexact, ceil-in (each side up to a whole inch) or nearest-inexact

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, closed-world), the description discloses meaningful conditional behavior: total weight, density in lb/ft³ and kg/m³, and ocean weight/measurement are returned only when every item carries a weight, and ocean measure is the larger of m³ and tonnes. It also explains the three rounding modes. It does not state what happens on partial weight input, leaving a small gap.

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?

Three sentences, front-loaded with the purpose before inputs and conditional outputs; almost every clause carries information. Minor redundancy in repeating defaults (in, quantity 1, rounding exact) that the schema already encodes. No filler or throat-clearing.

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 carries the burden of describing return values: volume across five units plus the conditional weight, density and ocean measure outputs. It also defines the rounding behaviors that the enum alone would not convey. The omission is per-line versus aggregate output structure, plus the failure mode for mixed weight presence.

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?

Schema coverage is 50%, with unit, quantity, weightUnit and weightBasis carrying only enums and defaults, so the description must compensate. It does add real value by spelling out the allowed unit set and default (in), quantity default 1, and how weight interacts with weightBasis. However, it largely restates defaults rather than adding new semantics, and weightBasis's line-level meaning is only briefly touched.

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?

Opens with a specific verb-and-resource statement: total volume of up to 20 lines of identical pieces, enumerating the output units (cubic feet, cubic metres, cubic inches, cubic yards, litres). It is unmistakably a volume calculator. It does not explicitly contrast itself with siblings such as calculate_dim_weight or calculate_ti_hi, so it stops just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is for shipment cube when volume (not dimensional weight or pallet count) is needed. There is no explicit when-to-use, when-not-to-use, or named alternative. The one conditional it does give (weight-dependent outputs) is descriptive, not routing guidance.

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