Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_intermodal_rail_vs_truck

Calculates intermodal rail versus over-the-road truck breakeven by comparing container costs, transit lead time, and CO2e reductions for logistics corridor decisions.

Instructions

Intermodal Rail vs Over-The-Road (OTR) Trucking Breakeven. Compare cost per container, transit lead time, and carbon emission (CO₂e) reductions between domestic intermodal rail and long-haul OTR trucking. Discipline: LOGISTICS. Governing mathematical model / formula: Intermodal Savings = OTR Trucking Rate - (Drayage Origin + Rail Linehaul + Drayage Destination).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of intermodal_savings_dollars (Net Intermodal Cost Savings), total_intermodal_cost (Total Intermodal Cost), co2_reduction_metric_tons (Carbon Emissions Saved (CO₂e)), transit_time_differential (Estimated Transit Differential) using corridor_miles (Shipping Corridor Distance (Miles) in miles), otr_truck_rate (Direct OTR Trucking Rate ($)), rail_linehaul_cost (Rail Ramp-to-Ramp Cost ($)), drayage_both_ends (Combined Drayage Cost (Origin + Dest)). 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 'Intermodal Rail vs Over-The-Road (OTR) Trucking Breakeven' 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): "intermodal-rail-vs-truck"

    • category (string): "logistics"

    • name (string): "Intermodal Rail vs Over-The-Road (OTR) Trucking Breakeven"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.intermodal_savings_dollars (Net Intermodal Cost Savings): Formatted display string (e.g. '$700.00 (21.9% Saved)')

      • metrics.total_intermodal_cost (Total Intermodal Cost): Formatted display string (e.g. '$2,500.00')

      • metrics.co2_reduction_metric_tons (Carbon Emissions Saved (CO₂e)): Formatted display string (e.g. '2.4 Metric Tons (67% Cut)')

      • metrics.transit_time_differential (Estimated Transit Differential): Formatted display string (e.g. '+1.5 Days vs Direct OTR')

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

Input Schema

NameRequiredDescriptionDefault
corridor_milesNoShipping Corridor Distance (Miles) (miles). Intermodal is most competitive on lanes > 700 miles. Default: 1450. Min: 400. Max: 3500.
otr_truck_rateNoDirect OTR Trucking Rate ($). Dedicated solo driver dry van quote. Default: 3200. Min: 800. Max: 9000.
drayage_both_endsNoCombined Drayage Cost (Origin + Dest). Local trucking to and from rail ramps. Default: 850. Min: 250. Max: 2000.
rail_linehaul_costNoRail Ramp-to-Ramp Cost ($). Rail carrier ramp-to-ramp flat rate. Default: 1650. Min: 500. Max: 5000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/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 so: it declares deterministic floating-point precision, read-only/idempotent/stateless operation with zero side effects, bound-checked input validation, and safe diagnostic errors instead of thrown exceptions. It also documents the full return payload structure, which is needed since no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The header-based structure is clear and front-loaded, with the formula stated early. However, it is verbose: the RETURNS block enumerates field types and example strings anywhere from seven to ten times, which is a lot of text for a four-parameter tool, and the WHEN TO USE list restates the parameter names rather than explaining them concisely.

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?

For a straightforward deterministic calculator with no annotations and no output schema, the description covers everything an agent needs: what it computes, the exact formula, how to interpret inputs, what the returned metrics mean (including formatted display strings), error behavior, and which sibling to use instead. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and every parameter carries a description with units, defaults, and min/max bounds, so the schema already does the heavy lifting. The description reinforces this by mapping each input to its role in the formula (drayage origin+destination, rail ramp-to-ramp linehaul), adding interpretive context rather than repeating the schema verbatim.

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+resource pair (compare intermodal rail vs OTR trucking breakeven) and names the three computed dimensions: cost per container, transit lead time, and CO2e reduction. The governing formula is spelled out, so an agent can tell exactly what this tool computes versus a generic dispatcher.

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 names each output metric (intermodal_savings_dollars, total_intermodal_cost, co2_reduction_metric_tons, transit_time_differential) and its driving inputs, plus a WHEN NOT TO USE clause excluding qualitative reasoning and non-numeric inputs. Disambiguation routes the agent to omni_universal_query, omni_batch_calculate, and omni_describe_solver by condition.

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