Skip to main content
Glama

Calculate car trip cost

calculate_trip_cost
Read-onlyIdempotent

Estimate the true cost of driving from one place to another: fuel or electricity, maintenance, tyres, tolls and optionally ownership costs (depreciation, insurance, registration). Best coverage in Europe. Returns EUR figures with a breakdown. Estimates use vehicle-class averages. Motorway vignettes for Austria, Switzerland, Czechia, Slovakia and Slovenia are included in tolls_and_extras (see the vignettes list); other vignette countries such as Hungary are flagged in warnings but not yet priced.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "calculate_trip_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination, e.g. "Salzburg, Austria".
fromYesStart location, city or address. Include the country, e.g. "Munich, Germany".
premiumNoPremium brand: servicing, tyres and ownership cost more.
fuel_typeNoOnly for classes other than hybrid and electric. Default petrol.
fuel_priceNoOptional override: EUR per litre (or per kWh for electric).
round_tripNoDouble the distance, tolls and costs.
vehicle_classNoType of vehicle.compact_car
include_ownership_costsNoAdd depreciation, insurance and registration/finance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the tool as read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds substantial behavior beyond that: estimates use vehicle-class averages, return EUR figures with a breakdown, include specific vignette countries in tolls_and_extras, and flag unsupported vignette countries in warnings.

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?

The description is front-loaded with purpose and output expectations, and each sentence carries relevant information. The final sentence is dense but earns its place by documenting vignette coverage limits, though 'Best coverage in Europe' is slightly less precise than the rest.

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 complex estimation tool with no output schema, the description covers the important context: what is included in the cost, how estimates are derived, the return currency and breakdown, regional coverage, and toll/vignette limitations. An agent has enough information to invoke it correctly.

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 still adds useful meaning by stating that estimates use vehicle-class averages, distinguishing fuel/electricity costs, and elaborating optional ownership costs, which helps an agent interpret key parameters beyond the schema's field descriptions.

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 names a specific verb and resource: estimating the cost of driving a trip. It lists the cost components covered and clarifies that results are EUR estimates with a breakdown, which is enough for an agent to identify the tool's function without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly establishes the use case as car-trip cost estimation with optional ownership costs and notes strongest coverage in Europe. There are no sibling tools to route between, but it stops short of explicit exclusions such as non-car travel or exact-cost scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources