Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

chargeable_weight_calculator

Read-onlyIdempotent

Calculates air freight chargeable weight by comparing actual weight and volumetric weight using IATA standard or custom divisor. Determines if cargo is volumetric (light) or heavy based on ratio.

Instructions

Calculate air freight chargeable weight (volumetric vs actual).

Airlines charge by "chargeable weight" — the greater of actual weight or volumetric weight. The IATA standard volumetric factor is 6,000 (1 CBM = 166.67 kg). Some carriers use different factors (e.g., 5,000 for DHL).

Use this tool when you need to:

  • Quote air freight shipments

  • Determine if a shipment is charged by volume or weight

  • Compare volumetric factors across carriers

A ratio > 1.0 means the shipment is "volumetric" (light for its size). A ratio < 1.0 means it's "heavy" (dense cargo).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
length_cmYesLength in centimetres
width_cmYesWidth in centimetres
height_cmYesHeight in centimetres
gross_weight_kgYesActual gross weight in kilograms
piecesNoNumber of identical pieces (default: 1)
factorNoVolumetric divisor (default: 6000 IATA standard, DHL uses 5000)
Behavior4/5

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint. Description adds IATA standard factor explanation and ratio interpretation (>1.0 = volumetric, <1.0 = heavy). No contradictions.

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?

Four paragraphs, well-structured with clear first sentence. No fluff, but could be slightly more concise by merging some lines.

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?

No output schema, so agent relies on description for return format. Ratio interpretation is provided, but explicit return fields are missing. Adequate but incomplete.

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 100% with descriptions for all parameters. Description adds overall context about factor default but not enough to raise above baseline.

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 states 'Calculate air freight chargeable weight (volumetric vs actual).' Verb 'calculate' and resource 'chargeable weight' are specific. Distinguishes from siblings like cbm_calculator (pure volume) and ldm_calculator.

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?

Explicitly lists use cases: quoting shipments, determining charge type, comparing factors. Does not mention when not to use, but context is clear enough for an agent to infer.

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