Skip to main content
Glama

Plan motorway vignettes and separate tolls

plan_motorway_vignettes
Read-onlyIdempotent

Plan a dated passenger-car trip through Czechia, Austria, Hungary, Slovakia, Slovenia, Romania, Bulgaria, Switzerland and Moldova. Compare verified vignette validity, official links, separately payable tolls and optional VignetteGO quotes.

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": {
      "vehicle": "<vehicle>",
      "crossings": "<crossings>"
    },
    "name": "plan_motorway_vignettes"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehicleYes
currencyNoCommercial quote currency. Official prices stay in the operator’s original currency.EUR
languageNoUser response and commercial website handoff language. Translate any detailed reference text to this language when presenting it.en
crossingsYesEvery local calendar day of motorway use, separately by country and direction, including additional days and midnight crossings. No automatic routing from city names.
journey_typeNoWhen omitted infer a return only from supplied return crossings.
purchase_dateNoEarliest planned purchase date, local YYYY-MM-DD. Defaults to today.
asymmetric_route_confirmedNoSet true only when the traveller confirms that the opposite direction deliberately skips a listed country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behaviour, so the safety profile is covered. The description adds useful context on what the response covers (verified validity, official links, separately payable tolls, optional commercial quotes), but says nothing about failure modes, how unknown segment identifiers are handled, or how official pricing versus quotes are distinguished in behaviour.

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?

Two sentences, front-loaded with the action and geographic scope, followed by the comparison outputs. No filler; the country list is long but functionally necessary to bound the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested objects, 7 parameters, strict enums and no output schema, the description covers intent and output categories but omits the operational rules the caller must respect (per-day, per-country, per-direction crossings; confirmed-class requirements; no city-name routing). Those rules live only in the schema, so the description is adequate but not self-sufficient.

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 86%, so the schema already carries the parameter burden. The description contributes only the framing concepts of a 'dated' trip and 'passenger-car' scope, which map loosely to the date-bearing crossings and vehicle.category fields; it adds little semantics the schema does not already state explicitly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Plan a dated passenger-car trip' through an enumerated list of countries, then states what the plan contains (vignette validity, official links, separately payable tolls, optional quotes). It is clearly differentiable from list_vignette_catalogue by verb, though the distinction is implicit rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by 'Plan a dated passenger-car trip' — an agent can infer this is for trip-level vignette planning rather than catalogue browsing. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g. confirmed vehicle class data), and no named alternative such as list_vignette_catalogue.

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