Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_true_cost_to_own

Calculates a vehicle's 5-year true cost to own by combining depreciation, financing, fuel, insurance, maintenance, and taxes, returning total, monthly, per-mile, and depreciation-share costs.

Instructions

5-Year True Cost to Own (TCO) Calculator. Calculate true full cost to own a vehicle over 5 years combining depreciation, financing interest, fuel, insurance, maintenance, and state taxes. Discipline: FINANCE. Governing mathematical model / formula: 5-Yr TCO = Depreciation + Financing + Insurance + Fuel + Maintenance + Taxes/Fees.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_5yr_tco (Total 5-Year True Cost to Own), monthly_effective_tco (Effective Monthly Cost of Ownership), cost_per_mile_tco (True Cost per Mile (13.5k mi/yr)), depreciation_share (Depreciation Share of Total Cost) using purchase_price_tco (Vehicle Purchase Price), monthly_fuel_cost (Estimated Monthly Fuel / Power Cost), monthly_insurance (Monthly Auto Insurance Premium), loan_interest_total (Total 5-Year Financing Interest Paid). 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 '5-Year True Cost to Own (TCO) 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): "true-cost-to-own"

    • category (string): "finance"

    • name (string): "5-Year True Cost to Own (TCO) Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_5yr_tco (Total 5-Year True Cost to Own): Formatted display string (e.g. '$52,600.00')

      • metrics.monthly_effective_tco (Effective Monthly Cost of Ownership): Formatted display string (e.g. '$876.67 / mo')

      • metrics.cost_per_mile_tco (True Cost per Mile (13.5k mi/yr)): Formatted display string (e.g. '$0.78 / mile')

      • metrics.depreciation_share (Depreciation Share of Total Cost): Formatted display string (e.g. '$24,000.00 (45.6%)')

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

Input Schema

NameRequiredDescriptionDefault
monthly_fuel_costNoEstimated Monthly Fuel / Power Cost. Gas or electricity expenditure. Default: 175. Min: 20. Max: 1500.
monthly_insuranceNoMonthly Auto Insurance Premium. Full coverage insurance premium. Default: 160. Min: 30. Max: 1000.
purchase_price_tcoNoVehicle Purchase Price. Total negotiated price. Default: 40000. Min: 5000. Max: 250000.
loan_interest_totalNoTotal 5-Year Financing Interest Paid. Interest accrued on auto loan. Default: 4500. Min: 0. Max: 40000.

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 provided, so the description carries the full burden and does so: it declares the tool read-only, idempotent, stateless, and side-effect free, and specifies that out-of-bounds inputs return a safe diagnostic error rather than throwing. It also discloses the deterministic floating-point execution model, which is the key behavioral fact for a calculator.

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?

Front-loaded with purpose and formula, then cleanly sectioned into usage, boundaries, behavior, and returns. It is longer than strictly necessary — the RETURNS block restates metric labels already implied — but since no output schema exists, that detail largely earns its place.

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 4-parameter stateless calculator with no output schema and no annotations, the description covers purpose, inputs, outputs, error behavior, and sibling routing. Nothing an agent needs in order to call it correctly and interpret the response is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds value by tying inputs to outputs (e.g. which parameter feeds which metric) and by disclosing the embedded assumptions '13.5k mi/yr' and the 5-year horizon, neither of which appears in the schema. It stops short of elaborating on units or default-override behavior beyond what the schema already contains.

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?

The description opens with a specific verb and resource ('Calculate true full cost to own a vehicle over 5 years') and states the governing formula (Depreciation + Financing + Insurance + Fuel + Maintenance + Taxes/Fees). An agent immediately knows this is the TCO calculator and what it computes, distinct from cost tools for other domains.

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 the exact output metrics and input parameters, WHEN NOT TO USE excludes qualitative reasoning, and the disambiguation section routes to omni_universal_query for generic queries, omni_batch_calculate for chained jobs, and omni_describe_solver for schema inspection. Alternatives and the conditions selecting them are stated rather than inferred.

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