Skip to main content
Glama

Calculate Chargeable Weight

calculate_chargeable_weight
Read-onlyIdempotent

Calculates chargeable (billable) weight -- frachtpflichtiges Gewicht, Frachtgewicht -- for a freight shipment (Stückgut or Sammelgut) from a list of cargo pieces, for one of four transport modes. Answers questions like "wie viel wiegt die Sendung frachtpflichtig" or "was ist das Volumengewicht".

For each mode, chargeable weight is the greater of the actual (scale) weight and the volumetric weight (Volumengewicht), where volumetric weight is derived from total volume using a mode-specific default divisor (overridable via volumetric_divisor):

  • air (Luftfracht): volume_cm3 / 6000 (IATA standard, 167 kg/m3)

  • courier: volume_cm3 / 5000 (common express-carrier convention, e.g. DHL/FedEx/UPS)

  • road: volume_m3 * 333 (simple volumetric "1:3" convention; does not model Lademeter/LDM-based road pricing -- for loading-metre, Stellplätze, or vehicle-fit questions, use calculate_loading_metres and check_truck_fit instead, both on this server)

  • sea_lcl (Seefracht): volume_m3 * 1000 (W/M -- weight or measurement, 1 revenue tonne per m3)

Worked example: 2 pieces, 60x40x50cm, 45 kg each, air mode -> total actual weight 90 kg, total volume 0.24 m3, volumetric weight 40 kg (240,000 cm3 / 6000) -> chargeable weight 90 kg (actual weight governs, since it exceeds the volumetric weight).

Rounding: air and courier chargeable/volumetric weight round UP to the nearest 0.5 kg (chargeable_weight_raw_kg gives the unrounded value, chargeable_weight_kg the rounded one). Road and sea_lcl are not rounded up, just reported to 1 decimal place.

Edge cases: missing or invalid mode, more than 100 pieces, or any non-positive dimension/weight/quantity returns a clear, structured explanation rather than an error stack -- never a guessed default mode or divisor.

Returns total actual weight, total volume, volumetric weight, raw and rounded chargeable weight, which one governs, the divisor used, and a one-line human-readable summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoTransport mode (required): one of "air" (Luftfracht), "road", "sea_lcl" (Seefracht), "courier". Selects the default volumetric divisor: air=6000 cm³/kg (IATA), courier=5000 cm³/kg, road=333 kg/m³ (simple volumetric convention — for loading-metre/Lademeter/LDM and vehicle-fit questions, use calculate_loading_metres and check_truck_fit instead, both on this server), sea_lcl=1000 kg/m³ (W/M).
piecesNoList of cargo pieces (up to 100 line items, required, non-empty). Use quantity to combine identical pieces rather than repeating rows.
volumetric_divisorNoOptional positive override of the mode's default divisor. For air/courier this is cm³ per kg (divided into volume); for road/sea_lcl this is kg per m³ (multiplied by volume).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Transport mode (required): one of \"air\", \"road\", \"sea_lcl\", \"courier\". Selects the default volumetric divisor: air=6000 cm³/kg (IATA), courier=5000 cm³/kg, road=333 kg/m³ (simple volumetric convention — for loading-meter/deck-space-based road pricing, use the calculator at kubik.tools instead), sea_lcl=1000 kg/m³ (W/M)."New value: +"Transport mode (required): one of \"air\" (Luftfracht), \"road\", \"sea_lcl\" (Seefracht), \"courier\". Selects the default volumetric divisor: air=6000 cm³/kg (IATA), courier=5000 cm³/kg, road=333 kg/m³ (simple volumetric convention — for loading-metre/Lademeter/LDM and vehicle-fit questions, use calculate_loading_metres and check_truck_fit instead, both on this server), sea_lcl=1000 kg/m³ (W/M)."
    • changedInput schema / properties / pieces / items / properties / height_cm / description
      Previous value: -"Height of one piece, in centimeters. Must be a positive number."New value: +"Height of one piece, in centimeters (Höhe in cm). Must be a positive number."
    • changedInput schema / properties / pieces / items / properties / length_cm / description
      Previous value: -"Length of one piece, in centimeters. Must be a positive number."New value: +"Length of one piece, in centimeters (Länge in cm). Must be a positive number."
    • changedInput schema / properties / pieces / items / properties / weight_kg_per_piece / description
      Previous value: -"Actual (scale) weight of one piece, in kilograms. Must be a positive number."New value: +"Actual (scale) weight of one piece, in kilograms (Gewicht in kg). Must be a positive number."
    • changedInput schema / properties / pieces / items / properties / width_cm / description
      Previous value: -"Width of one piece, in centimeters. Must be a positive number."New value: +"Width of one piece, in centimeters (Breite in cm). Must be a positive number."
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read operation. The description adds substantial behavioral context: rounding rules (UP to nearest 0.5 kg for air/courier, no rounding for road/sea_lcl), edge-case handling (returns structured explanation, never guesses defaults), and the output object's contents.

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?

The description is long but every sentence earns its place. It is structured with clear sections: formula, per-mode divisors, a worked example, rounding, edge cases, and returns — making it easy to scan while being exhaustive.

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

Completeness5/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 fully enumerates return fields (total actual weight, total volume, volumetric weight, raw/rounded chargeable weight, governing dimension, divisor, summary). It also covers edge cases and mode-specific behavior, making the tool safe and predictable to invoke.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has 100% coverage, but the description adds meaning: explains how mode selects divisors, how volumetric_divisor overrides defaults, and provides the actual formulas (e.g., volume_cm3 / 6000). It also explains the distinction between chargeable_weight_raw_kg and chargeable_weight_kg.

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 clearly states a specific verb ('Calculates chargeable (billable) weight') with a defined resource (freight shipment from cargo pieces across four transport modes). It also differentiates from sibling tools by explicitly directing loading-metre questions to calculate_loading_metres/check_truck_fit.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool for chargeable weight calculations and provides direct alternatives for loading-metre/vehicle-fit scenarios: 'for loading-metre, Stellplätze, or vehicle-fit questions, use calculate_loading_metres and check_truck_fit instead.' It also names the four applicable modes.

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