Skip to main content
Glama

Roadcut — European road trips

Get a road trip overview

get_road_trip
Read-onlyIdempotent

Day-by-day overview of one Roadcut road trip: from, to, km and where to sleep each day, highlights, ferries, seasonal mountain passes on the way, a cost estimate, EV charging along the road (stations, fast chargers, longest stretch without one), and links to the full plan and the interactive planner. A trip is identified by its slug.

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": {
      "slug": "<slug>"
    },
    "name": "get_road_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the user, for the links (en, de, es, fr, it, cs, da, sv, nb, pl, nl). Default en.
slugYesRoute id, e.g. "bergen-to-geiranger".
travel_dateNoWhen the user will drive (YYYY-MM-DD), to check seasonal passes. Default today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description is not required to restate it. The description contributes value the annotations cannot: it enumerates the returned sections and notes that seasonal-pass information is part of the payload, which explains why travel_date matters. It does not describe error behaviour for an unknown slug, which keeps it below 5.

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 two sentences, front-loaded with the core scope ('Day-by-day overview of one Roadcut road trip') before the payload inventory. The long colon-separated list is dense but every item describes a distinct returned section, so it earns its space rather than padding. Minor cost: the enumeration is hard to scan in a single breath.

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

Completeness4/5

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

There is no output schema, so the description carries the full burden of saying what comes back, and it does so comprehensively across itinerary, costs, charging and links. With only three fully documented parameters and rich annotations, nothing structurally important is missing. The residual gap is failure behaviour on an invalid or unknown slug.

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 all three parameters (lang, slug, travel_date) are already documented in the input schema with formats, enum and defaults, putting this at the baseline of 3. The description adds only the framing that the slug identifies the trip; it does not explain how travel_date shifts the seasonal-pass output or how lang affects the returned links.

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 concrete resource ('one Roadcut road trip') and itemises exactly what the payload contains: from/to, km, sleep stops, highlights, ferries, seasonal passes, cost estimate, EV charging and links. That is far more specific than the title. It stops short of 5 because it never names its siblings, leaving the agent to infer that find_road_trips is the discovery counterpart that produces the slug.

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 only implied: 'A trip is identified by its slug' signals that the caller must already hold a slug, which loosely routes the agent to find_road_trips first, and the overview framing distinguishes it from get_mountain_pass and get_driving_rules. There is no explicit when-to-use/when-not statement, no mention of what to do if the slug is unknown, and no stated alternative for users who lack a slug.

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