Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

math_fuel_consumption_calculator

Read-onlyIdempotent

Convert fuel economy between US mpg, UK mpg, L/100km, and km/L. Estimate trip fuel cost from distance, consumption, and price.

Instructions

Fuel Consumption Calculator. Convert a fuel-economy figure between US mpg, UK (Imperial) mpg, L/100km, and km/L, or estimate the fuel and money a trip will cost given distance, vehicle consumption, and a per-litre or per-gallon fuel price. Returns the converted value (convertConsumption) or litres needed plus total cost in the price's native currency (tripCost). Use this for fuel-economy and trip-cost math; use math_unit_converter instead for general length / volume / speed unit conversion, and math_running_pace_converter for pace and speed. Pure local arithmetic: read-only, non-destructive, deterministic, contacts no external service, and is rate-limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes"convertConsumption" converts one economy value between units (needs value, fromUnit, toUnit). "tripCost" estimates trip fuel and cost (needs distance, distanceUnit, consumption, consumptionUnit, pricePerUnit, priceUnit).convertConsumption
valueNoconvertConsumption only: the fuel-economy value to convert, expressed in fromUnit. Must be greater than zero for mpg_us, mpg_uk, and km_per_l.
fromUnitNoconvertConsumption only: unit of the input value. mpg_us=miles per US gallon, mpg_uk=miles per Imperial gallon, l_per_100km=litres per 100km, km_per_l=kilometres per litre.
toUnitNoconvertConsumption only: unit to convert the value into. Same four enum values as fromUnit.
distanceNotripCost only: trip distance, expressed in distanceUnit.
distanceUnitNotripCost only: unit of distance. km=kilometres, mi=miles.
consumptionNotripCost only: the vehicle fuel economy, expressed in consumptionUnit. Must be greater than zero.
consumptionUnitNotripCost only: unit of the consumption figure. Same four enum values as fromUnit.
pricePerUnitNotripCost only: fuel price per volume unit, expressed in priceUnit currency and volume.
priceUnitNotripCost only: currency + volume the price refers to. Determines the output currency (USD/EUR/GBP) and the volume (US gallon, UK gallon, or litre) pricePerUnit is multiplied by.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoEchoes the operation that was run (defaults to convertConsumption when omitted).
dataNoconvertConsumption returns fromUnit/toUnit/fromValue/toValue/formattedFrom/formattedTo. tripCost returns distance/consumption/fuelNeeded/totalCost/pricePerUnit/currency and formatted strings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / consumption
      Added value: +{
+  "description": "tripCost only: the vehicle fuel economy, expressed in consumptionUnit. Must be greater than zero.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / consumptionUnit
      Added value: +{
+  "description": "tripCost only: unit of the consumption figure. Same four enum values as fromUnit.",
+  "enum": [
+    "mpg_us",
+    "mpg_uk",
+    "l_per_100km",
+    "km_per_l"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / distance
      Added value: +{
+  "description": "tripCost only: trip distance, expressed in distanceUnit.",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / distanceUnit
      Added value: +{
+  "description": "tripCost only: unit of distance. km=kilometres, mi=miles.",
+  "enum": [
+    "km",
+    "mi"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / fromUnit / description
      Added value: +"convertConsumption only: unit of the input value. mpg_us=miles per US gallon, mpg_uk=miles per Imperial gallon, l_per_100km=litres per 100km, km_per_l=kilometres per litre."
    • addedInput schema / properties / fromUnit / enum
      Added value: +[
+  "mpg_us",
+  "mpg_uk",
+  "l_per_100km",
+  "km_per_l"
+]
    • addedInput schema / properties / operation / default
      Added value: +"convertConsumption"
    • addedInput schema / properties / operation / description
      Added value: +"\"convertConsumption\" converts one economy value between units (needs value, fromUnit, toUnit). \"tripCost\" estimates trip fuel and cost (needs distance, distanceUnit, consumption, consumptionUnit, pricePerUnit, priceUnit)."
    • addedInput schema / properties / operation / enum
      Added value: +[
+  "convertConsumption",
+  "tripCost"
+]
    • addedInput schema / properties / pricePerUnit
      Added value: +{
+  "description": "tripCost only: fuel price per volume unit, expressed in priceUnit currency and volume.",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / priceUnit
      Added value: +{
+  "description": "tripCost only: currency + volume the price refers to. Determines the output currency (USD/EUR/GBP) and the volume (US gallon, UK gallon, or litre) pricePerUnit is multiplied by.",
+  "enum": [
+    "usd_per_gal_us",
+    "usd_per_gal_uk",
+    "usd_per_l",
+    "eur_per_l",
+    "gbp_per_l",
+    "gbp_per_gal_uk"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / toUnit / description
      Added value: +"convertConsumption only: unit to convert the value into. Same four enum values as fromUnit."
    • addedInput schema / properties / toUnit / enum
      Added value: +[
+  "mpg_us",
+  "mpg_uk",
+  "l_per_100km",
+  "km_per_l"
+]
    • addedInput schema / properties / value / description
      Added value: +"convertConsumption only: the fuel-economy value to convert, expressed in fromUnit. Must be greater than zero for mpg_us, mpg_uk, and km_per_l."
    • addedInput schema / properties / value / minimum
      Added value: +0
    • changedInput schema / properties / value / type
      Previous value: -"integer"New value: +"number"
    • changedInput schema / required
      Previous value: -[
-  "operation",
-  "value",
-  "fromUnit",
-  "toUnit"
-]New value: +[
+  "operation"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "convertConsumption returns fromUnit/toUnit/fromValue/toValue/formattedFrom/formattedTo. tripCost returns distance/consumption/fuelNeeded/totalCost/pricePerUnit/currency and formatted strings.",
+      "properties": {
+        "consumption": {
+          "description": "tripCost: fuel economy in its original unit.",
+          "type": "number"
+        },
+        "costFormatted": {
+          "description": "tripCost: total cost with currency, e.g. \"$48 USD\".",
+          "type": "string"
+        },
+        "currency": {
+          "description": "tripCost: ISO 4217 currency of totalCost, derived from priceUnit.",
+          "enum": [
+            "USD",
+            "EUR",
+            "GBP"
+          ],
+          "type": "string"
+        },
+        "distance": {
+          "description": "tripCost: trip distance in its original unit.",
+          "type": "number"
+        },
+        "distanceFormatted": {
+          "description": "tripCost: distance with unit, e.g. \"400 km\".",
+          "type": "string"
+        },
+        "formattedFrom": {
+          "description": "convertConsumption: input value with unit symbol, e.g. \"30 mpg (US)\".",
+          "type": "string"
+        },
+        "formattedTo": {
+          "description": "convertConsumption: converted value with unit symbol.",
+          "type": "string"
+        },
+        "fromUnit": {
+          "description": "convertConsumption: source economy unit.",
+          "type": "string"
+        },
+        "fromValue": {
+          "description": "convertConsumption: input value as supplied.",
+          "type": "number"
+        },
+        "fuelFormatted": {
+          "description": "tripCost: fuel needed with unit, e.g. \"32 L\".",
+          "type": "string"
+        },
+        "fuelNeeded": {
+          "description": "tripCost: fuel required for the trip, in litres.",
+          "type": "number"
+        },
+        "pricePerUnit": {
+          "description": "tripCost: fuel price per unit as supplied.",
+          "type": "number"
+        },
+        "toUnit": {
+          "description": "convertConsumption: target economy unit.",
+          "type": "string"
+        },
+        "toValue": {
+          "description": "convertConsumption: converted value in toUnit.",
+          "type": "number"
+        },
+        "totalCost": {
+          "description": "tripCost: total fuel cost in the price unit currency.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "operation": {
+      "description": "Echoes the operation that was run (defaults to convertConsumption when omitted).",
+      "enum": [
+        "convertConsumption",
+        "tripCost"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

The description adds behavioral context beyond the annotations, stating it is 'read-only, non-destructive, deterministic, contacts no external service, and is rate-limited.' These details align with and supplement the annotation hints, providing full transparency.

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

Conciseness5/5

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

The description is concise with three sentences: first explaining core conversions, second specifying return values, third giving usage guidance and behavioral notes. It is front-loaded with the core purpose and every sentence adds value.

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?

Given the 10 parameters, 100% schema coverage, and presence of an output schema, the description provides sufficient context by explaining the two operations and their outputs. It is complete enough for an agent to understand the tool's capabilities.

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?

The input schema has 100% coverage, but the description adds value by summarizing the return values for each operation: 'Returns the converted value (convertConsumption) or litres needed plus total cost in the price's native currency (tripCost).' This helps the agent understand what to expect without reading the schema.

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 clearly states the tool as a fuel consumption calculator with two specific operations: convertConsumption and tripCost. It distinguishes itself from sibling tools like math_unit_converter and math_running_pace_converter, making its purpose unambiguous.

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?

The description explicitly provides context for when to use this tool versus alternatives, stating 'Use this for fuel-economy and trip-cost math; use math_unit_converter instead for general length / volume / speed unit conversion, and math_running_pace_converter for pace and speed.' This gives clear guidance on tool selection.

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