Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

chargeable_weight_calculator

Read-onlyIdempotent

Calculate air freight chargeable weight by comparing actual gross weight and volumetric weight to determine the billable amount.

Instructions

Calculate air freight chargeable weight — the greater of actual gross weight and volumetric weight, which is what airlines bill. Volumetric weight (kg) = (L x W x H in cm) / divisor; the IATA-standard divisor is 6,000 (1 CBM = 166.67 kg), while express integrators (DHL, FedEx, UPS) typically use 5,000.

Behavior: deterministic; per-piece volumetric weight is rounded to 2 decimal places before totalling; basis reports which weight governs ("volumetric" = cargo is light for its size, "actual" = dense). Air mode only — sea W/M (1 CBM = 1,000 kg) is covered by consignment_calculator with mode=sea. Missing or non-positive inputs error with the failing parameter named. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits.

Returns: chargeable_weight_kg, basis, volumetric_weight_kg (total and per piece), gross_weight_kg, cbm, ratio, factor and pieces under result; normalized_input echoes the interpreted inputs and any defaults applied; plus confidence, _source and citation (the FreightUtils v1 response envelope).

Related: cbm_calculator (volume only), consignment_calculator (multi-line, all modes), uld_lookup (the equipment the freight flies in).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
factorNoVolumetric divisor in cm³/kg. Default: 6000 (IATA standard); express carriers typically 5000.
piecesNoNumber of identical pieces. Default: 1.
width_cmYesWidth of one piece in centimetres (> 0). Example: 80.
height_cmYesHeight of one piece in centimetres (> 0). Example: 100.
length_cmYesLength of one piece in centimetres (> 0). Example: 120.
gross_weight_kgYesActual gross weight of the WHOLE shipment (all pieces) in kilograms. Example: 500.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
resultYes
_sourceYes
citationYes
validityNo
warningsNo
confidenceYes
blocking_errorsNo
envelope_versionYes
normalized_inputNo
Behavior5/5

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

Adds significant behavioral context beyond annotations: deterministic behavior, rounding to 2 decimal places, error handling for missing/non-positive inputs with parameter naming, rate limit details with retry instructions. Annotations indicate readOnlyHint, idempotentHint, destructiveHint=false, which are consistent with description.

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?

Description is long but well-structured with clear paragraphs for purpose, behavior, returns, and related tools. Front-loads core purpose. Could be slightly trimmed without losing information, but remains effective.

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?

Comprehensive coverage: purpose, formula, behavior, error handling, rate limiting, return format (summarized), and sibling tools. Output schema exists but description still outlines key fields. Nothing critical omitted.

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 has 100% description coverage for all 6 parameters. Description adds context about defaults (factor defaults to 6000, pieces defaults to 1) and clarifies that gross_weight_kg is for the whole shipment. This adds value beyond schema descriptions, earning a 4.

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?

Description clearly states the tool calculates air freight chargeable weight, explains the formula, and distinguishes from siblings like cbm_calculator, consignment_calculator, and uld_lookup. The verb 'calculate' and specific resource 'chargeable weight' are well-defined.

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?

Explicitly states when to use (air freight only) and provides alternatives for sea freight (consignment_calculator with mode=sea). Also mentions rate limits and when to call get_subscribe_link for higher limits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SoapyRED/freightutils-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server