Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_fleet_tco_per_mile

Calculates total cost of ownership and operating cost per mile for commercial Class 8 tractors using fuel, driver, lease, maintenance, tire, and insurance inputs.

Instructions

Fleet Total Cost of Ownership (TCO) & Operating Cost Per Mile. Calculate total cost of ownership (TCO) and marginal cost per mile (MCPM) for commercial Class 8 tractors (fuel, driver, lease, maintenance, tires, insurance). Discipline: LOGISTICS. Governing mathematical model / formula: Cost Per Mile (CPM) = (Fixed Annual Overhead / Annual Miles) + Variable Operating Cost Per Mile.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_cost_per_mile (Total Operating Cost Per Mile), annual_total_operating_cost (Total Annual Cost Per Tractor), fuel_cost_per_mile (Fuel Cost Per Mile (6.5 MPG)), fixed_overhead_per_mile (Fixed Equipment Overhead) using annual_truck_miles (Annual Miles Driven Per Truck in miles/yr), driver_pay_cpm (Driver Wage & Benefits ($/Mile)), diesel_price_gal (Average Diesel Fuel Price ($/gal)), truck_lease_mo (Monthly Truck & Trailer Lease Payment ($)), annual_insurance_cost (Annual Commercial Truck Insurance ($)). 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 'Fleet Total Cost of Ownership (TCO) & Operating Cost Per Mile' 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): "fleet-tco-per-mile"

    • category (string): "logistics"

    • name (string): "Fleet Total Cost of Ownership (TCO) & Operating Cost Per Mile"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_cost_per_mile (Total Operating Cost Per Mile): Formatted display string (e.g. '$2.05 / mile')

      • metrics.annual_total_operating_cost (Total Annual Cost Per Tractor): Formatted display string (e.g. '$225,500.00 / yr')

      • metrics.fuel_cost_per_mile (Fuel Cost Per Mile (6.5 MPG)): Formatted display string (e.g. '$0.61 / mile')

      • metrics.fixed_overhead_per_mile (Fixed Equipment Overhead): Formatted display string (e.g. '$0.39 / mile')

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

Input Schema

NameRequiredDescriptionDefault
driver_pay_cpmNoDriver Wage & Benefits ($/Mile). Base wage per mile plus payroll tax and health benefits. Default: 0.72. Min: 0.4. Max: 1.2.
truck_lease_moNoMonthly Truck & Trailer Lease Payment ($). Financing or lease cost per equipment unit. Default: 2400. Min: 800. Max: 4500.
diesel_price_galNoAverage Diesel Fuel Price ($/gal). Average diesel fuel pump price. Default: 3.95. Min: 2. Max: 6.5.
annual_truck_milesNoAnnual Miles Driven Per Truck (miles/yr). Typical OTR truck covers 100k-125k miles/year. Default: 110000. Min: 25000. Max: 200000.
annual_insurance_costNoAnnual Commercial Truck Insurance ($). Primary auto liability, cargo, and physical damage. Default: 14500. Min: 5000. Max: 35000.

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 read-only, idempotent, stateless behavior with zero side effects, describes deterministic floating-point execution, and explains that out-of-bounds inputs return a safe diagnostic error rather than throwing. It even documents the response envelope and latency field.

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?

Section headings and a front-loaded title/formula give it good structure, but the WHEN TO USE bullet enumerates all five parameters with parenthetical units already fully documented in the schema, which is padding. The RETURNS block is also long for what is essentially a fixed envelope.

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 five-parameter calculator with no output schema, the description supplies the governing formula, the unit conventions, the default-bearing behavior, the error path, and a full description of the metrics returned. Nothing an agent needs in order to invoke it correctly 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 coverage is 100% and each parameter already carries type, default, and min/max bounds, so the baseline of 3 applies. The description restates parameter names and units in the WHEN TO USE block but adds no new semantics such as how driver_pay_cpm interacts with annual_truck_miles in the formula.

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 Fleet TCO and marginal cost per mile for Class 8 tractors, and names the exact outputs (total_cost_per_mile, fuel_cost_per_mile, fixed_overhead_per_mile). It also explicitly distinguishes itself from omni_universal_query and omni_batch_calculate, so an agent can route 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 explicit WHEN TO USE with the output/input pairing, a WHEN NOT TO USE clause excluding qualitative or non-numeric requests, and named alternatives for chained jobs and schema inspection. The only weakness is that the exclusion ('qualitative evaluations') is generic, but the routing guidance itself is complete.

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