Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_air_freight_chargeable_weight

Calculate IATA air freight chargeable weight by comparing volumetric and gross weight, then estimate total freight cost to avoid airline volume surcharges.

Instructions

Air Freight Volumetric vs Gross Chargeable Weight Calculator. Calculate IATA international air freight volumetric chargeable weight (1:6000 ratio = 167 kg/m³) and avoid costly airline volume surcharges. Discipline: LOGISTICS. Governing mathematical model / formula: Volumetric Weight (kg) = (Length × Width × Height in cm) / 6,000 | Chargeable Weight = Max(Gross kg, Volumetric kg).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of chargeable_weight_kg (IATA Chargeable Weight), volumetric_weight_kg (Volumetric Air Weight), total_air_freight_cost (Total Estimated Air Freight Bill), volume_ratio_status (Air Cargo Rating Status) using air_length_cm (Package Length (cm) in cm), air_width_cm (Package Width (cm) in cm), air_height_cm (Package Height (cm) in cm), air_gross_kg (Actual Scale Gross Weight (kg) in kg), rate_per_kg_usd (Air Freight Base Rate ($/kg)). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Air Freight Volumetric vs Gross Chargeable Weight Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "air-freight-chargeable-weight"

    • category (string): "logistics"

    • name (string): "Air Freight Volumetric vs Gross Chargeable Weight Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.chargeable_weight_kg (IATA Chargeable Weight): Formatted display string (e.g. '160.0 kg')

      • metrics.volumetric_weight_kg (Volumetric Air Weight): Formatted display string (e.g. '160.0 kg')

      • metrics.total_air_freight_cost (Total Estimated Air Freight Bill): Formatted display string (e.g. '$768.00')

      • metrics.volume_ratio_status (Air Cargo Rating Status): Formatted display string (e.g. 'Volume Cargo (+39% Surcharge)')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_air_freight_chargeable_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
air_gross_kgNoActual Scale Gross Weight (kg) (kg). Physical gross weight in kilograms. Default: 115. Min: 1. Max: 5000.
air_width_cmNoPackage Width (cm) (cm). Cargo skid or box width. Default: 80. Min: 10. Max: 240.
air_height_cmNoPackage Height (cm) (cm). Cargo skid or box height. Default: 100. Min: 10. Max: 240.
air_length_cmNoPackage Length (cm) (cm). Cargo skid or box length. Default: 120. Min: 10. Max: 300.
rate_per_kg_usdNoAir Freight Base Rate ($/kg). All-in air cargo tariff per chargeable kg. Default: 4.8. Min: 1. Max: 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full behavioral burden and does: it declares the tool read-only, idempotent, stateless, and side-effect free. It also discloses that out-of-bounds inputs return a diagnostic error status rather than throwing, which is exactly the failure-mode information an agent needs before calling.

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?

Headings (USAGE, DISAMBIGUATION, BEHAVIOR, RETURNS) front-load the decision-relevant content and the formula appears in the first paragraph. Some filler creeps in, notably the marketing claim about 'eliminating LLM arithmetic mistakes and formula hallucinations,' which repeats the deterministic-computation point.

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?

There is no output schema, so the RETURNS section's enumeration of status, metrics keys, formatted display strings, and execution_time_ms is necessary and supplied. Combined with validation bounds and the input echo behavior, an agent has everything needed to call and parse the result.

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 description coverage is 100% with per-field descriptions, defaults, and min/max bounds, so the baseline of 3 applies. The description restates the five parameter names and their units but adds no interpretation beyond the formula itself, which the schema does not need repeated.

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?

States a specific verb (calculate) and resource (IATA air freight volumetric vs gross chargeable weight) and gives the governing formula (L×W×H/6000, max of gross vs volumetric). It explicitly distinguishes itself from the generic dispatcher omni_universal_query, so an agent can tell it apart from siblings without opening a schema.

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?

Provides an explicit WHEN TO USE block enumerating the computed outputs and required inputs, plus a WHEN NOT TO USE block excluding qualitative reasoning. The disambiguation section names concrete alternatives (omni_universal_query for generic dispatch, omni_batch_calculate for chained jobs, omni_describe_solver for schema inspection).

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

Deploy Server

Other Tools