Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_container_cbm_utilization

Calculate ocean container CBM volume, metric payload, and utilization for 20ft, 40ft, and 40ft HC shipments from carton count, dimensions, and weight.

Instructions

Ocean Shipping Container CBM Volume & Payload Calculator. Calculate cubic meter (CBM) volume, metric ton payload capacity, and container utilization percentage for 20ft, 40ft, and 40ft High Cube (HC) ocean containers. Discipline: LOGISTICS. Governing mathematical model / formula: Total CBM = Total Cartons × (Length × Width × Height in meters) | 1 CBM = 35.315 cu ft.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_cargo_cbm (Total Cargo Volume (CBM)), best_container_type (Recommended Container), total_cargo_mass_kg (Total Cargo Weight), weight_utilization_pct (Payload Weight Allowance) using carton_count (Total Number of Cartons in cartons), carton_l_cm (Carton Length (cm) in cm), carton_w_cm (Carton Width (cm) in cm), carton_h_cm (Carton Height (cm) in cm), carton_weight_kg (Weight per Carton (kg) in 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Ocean Shipping Container CBM Volume & Payload Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

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): "container-cbm-utilization"

    • category (string): "logistics"

    • name (string): "Ocean Shipping Container CBM Volume & Payload Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_cargo_cbm (Total Cargo Volume (CBM)): Formatted display string (e.g. '40.2 CBM')

      • metrics.best_container_type (Recommended Container): Formatted display string (e.g. '1x 40ft Standard (59% full)')

      • metrics.total_cargo_mass_kg (Total Cargo Weight): Formatted display string (e.g. '12,325 kg (12.33 MT)')

      • metrics.weight_utilization_pct (Payload Weight Allowance): Formatted display string (e.g. '46.5% of 26,500 kg limit')

    • 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_container_cbm_utilization"
  }
}

Input Schema

NameRequiredDescriptionDefault
carton_h_cmNoCarton Height (cm) (cm). External case height. Default: 30. Min: 10. Max: 150.
carton_l_cmNoCarton Length (cm) (cm). External case length. Default: 45. Min: 10. Max: 200.
carton_w_cmNoCarton Width (cm) (cm). External case width. Default: 35. Min: 10. Max: 150.
carton_countNoTotal Number of Cartons (cartons). Total packaged shipping cartons. Default: 850. Min: 10. Max: 10000.
carton_weight_kgNoWeight per Carton (kg) (kg). Weight per case in kilograms. Default: 14.5. Min: 0.5. Max: 100.

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 burden and does: it declares read-only, idempotent, stateless behavior with zero side effects, and explains that out-of-bounds inputs return a diagnostic error status rather than throwing. That is exactly the safety and failure-mode context 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?

Well front-loaded and sectioned (USAGE, BEHAVIOR, RETURNS), so an agent can scan it quickly. It loses a point for redundancy: the parameter roster inside WHEN TO USE repeats the schema, and doubled parentheticals like 'carton_count (Total Number of Cartons in cartons)' waste tokens.

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 and no annotations, the description compensates fully by documenting the response envelope (status, calculator, category, formula, inputs, metrics, execution_time_ms) and giving example formatted values for each metric. Nothing an agent needs to interpret the result is missing.

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%, and the schema already documents each parameter's meaning, units, defaults, and min/max bounds. The description mainly restates the parameter list (in a redundant 'X (Label in units)' style) rather than adding syntax or interaction semantics beyond it, so the baseline of 3 applies.

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 a precisely scoped resource: CBM volume, metric-ton payload, and utilization percentage for 20ft, 40ft, and 40ft HC containers. It also names the sibling it should be preferred over (omni_universal_query), so the agent can distinguish it without opening either 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?

Explicit WHEN TO USE, WHEN NOT TO USE (no qualitative reasoning; all inputs must be numeric), and SIBLING ROUTING sections give an agent a complete decision rule including the exclusion condition and the fallback dispatcher.

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