Skip to main content
Glama
Sign In

TollCalc MCP

by eu.tollcalc.app
OverviewDiscussionsAdmin

calculate_toll

Calculate European road toll costs for heavy trucks and commercial vehicles. Supports 40+ countries. Response fields (all detail levels): origin, destination (resolved place names), total_toll_eur (float), total_distance_km, toll_km, toll_free_km, countries (array with country, country_name, total_km, toll_km, toll_eur), info_url (link to view this route calculation in the TollCalc web app, including the planned route on an interactive map — share with colleagues or open in browser). With detail=detailed: countries also include segments (road, type, km, toll_eur). With detail=full: segments also include geometry, source_url, matched_geofence, formula_vars (all resolved formula variables: km, road_type, weight, axles, emission_class, co2_class, computed rate variables like tollRate, weightAxleClass, effective rate per km), and lookup_trace (all table lookups performed during calculation with their results); origin/destination include lat/lon coordinates.

Input Schema

NameRequiredDescriptionDefault
viaNoOptional intermediate waypoints (max 498; origin + via + destination must not exceed 500)
detailNoResponse detail level. compact (default): total + per-country summary. detailed: adds per-segment costs without geometry. full: adds routing debug info and geometry.compact
originYesStart point: city/address (e.g. 'Munich, Germany') or 'lat;lon' (e.g. '48.1374;11.5755')
vehicleYesVehicle parameters
destinationYesEnd point: city/address or 'lat;lon'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / via / description
      Previous value: -"Optional intermediate waypoints (max 48; origin + via + destination must not exceed 50)"New value: +"Optional intermediate waypoints (max 498; origin + via + destination must not exceed 500)"
  2. Changed1 schema field changed
    • changedInput schema / properties / via / description
      Previous value: -"Optional intermediate waypoints (max 15)"New value: +"Optional intermediate waypoints (max 48; origin + via + destination must not exceed 50)"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and substantially does so by enumerating response fields for all detail levels, including country summaries, segments, geometry, formula variables, and lookup traces. It does not, however, discuss side effects, auth requirements, rate limits, or error behavior.

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?

Purpose and scope are front-loaded, and the long response-field enumeration is justified because there is no output schema. The dense prose could be more structured with bullets, but every sentence serves a purpose.

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 nested vehicle object, five parameters, and no output schema, the description supplies detailed return-shape information across compact, detailed, and full modes. An agent can call this tool and understand what to expect from the response.

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 description coverage is 100%, so the baseline is 3. The description reinforces the effect of the detail parameter on the response, but adds no syntax or constraints beyond what the schema already documents.

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: 'Calculate European road toll costs for heavy trucks and commercial vehicles', with scope '40+ countries'. This clearly distinguishes it from the only sibling, get_quota, which is unrelated.

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

Usage Guidelines2/5

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

The description says what the tool does but gives no explicit when-to-use, when-not-to-use, prerequisites, or alternatives. Since the only sibling is unrelated, the omission is less harmful, but the guidance is still absent.

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

All TollCalc MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources