Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_freight_density_nmfc

Calculate shipment density in pounds per cubic foot and determine the NMFC freight class from pallet dimensions and weight for LTL rate pricing.

Instructions

Freight Density & NMFC Freight Class Calculator. Calculate shipment density in pounds per cubic foot (PCF) and determine the National Motor Freight Classification (NMFC) freight class for LTL shipping. Discipline: LOGISTICS. Governing mathematical model / formula: Density (PCF) = Total Weight (lbs) / (Length × Width × Height / 1,728).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of calculated_density_pcf (Shipment Density (PCF)), recommended_nmfc_class (Standard NMFC Freight Class), total_cubic_feet (Total Shipment Volume), ltl_rate_impact (Freight Rate Pricing Tier) using shipment_length_in (Pallet Length (Inches) in in), shipment_width_in (Pallet Width (Inches) in in), shipment_height_in (Pallet Height (Inches) in in), shipment_weight_lbs (Total Gross Weight (lbs) in lbs). 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 'Freight Density & NMFC Freight Class 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): "freight-density-nmfc"

    • category (string): "logistics"

    • name (string): "Freight Density & NMFC Freight Class Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.calculated_density_pcf (Shipment Density (PCF)): Formatted display string (e.g. '12.2 PCF')

      • metrics.recommended_nmfc_class (Standard NMFC Freight Class): Formatted display string (e.g. 'Class 85')

      • metrics.total_cubic_feet (Total Shipment Volume): Formatted display string (e.g. '53.3 cu ft')

      • metrics.ltl_rate_impact (Freight Rate Pricing Tier): Formatted display string (e.g. 'Medium Density (Standard)')

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

Input Schema

NameRequiredDescriptionDefault
shipment_width_inNoPallet Width (Inches) (in). Width of packaged skid. Default: 40. Min: 10. Max: 96.
shipment_height_inNoPallet Height (Inches) (in). Height from floor to top of load. Default: 48. Min: 10. Max: 108.
shipment_length_inNoPallet Length (Inches) (in). Length of packaged skid. Default: 48. Min: 10. Max: 120.
shipment_weight_lbsNoTotal Gross Weight (lbs) (lbs). Total scale weight including pallet. Default: 650. Min: 25. Max: 10000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares the tool read-only, idempotent, stateless, side-effect-free, and states that out-of-bounds inputs return a diagnostic error status rather than throwing. It also enumerates the return structure, so the agent knows the exact shape of a successful response.

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?

Clearly sectioned with the purpose and formula front-loaded, followed by usage, behavior, and returns. It is longer than strictly necessary — the RETURNS block and repeated calculator/category strings are verbose — but every section is relevant and the structure aids scanning.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter deterministic calculator with no output schema, the description supplies the formula, validation behavior, and full return shape, which is enough to call it correctly. The minor gap is that the NMFC class mapping logic is asserted but not explained, though the deterministic framing makes this acceptable.

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%, so defaults, min/max, and units are already documented in the schema. The description echoes parameter names with human labels (pallet length/width/height, gross weight including pallet) but adds little syntax or meaning beyond what the schema provides. Baseline 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 and resource: calculates shipment density (PCF) and NMFC freight class for LTL shipping, and even names the governing formula. This is clearly distinguishable from generic dispatchers and from generic density tools like omni_density_mass_volume.

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 section maps each input to the computed output, WHEN NOT TO USE excludes qualitative or non-numeric use, and SIBLING ROUTING names omni_universal_query as the generic alternative. Nothing about tool selection is left to inference.

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