Skip to main content
Glama

Roadcut — European road trips

Find road trips

find_road_trips
Read-onlyIdempotent

Search Roadcut's European road trip itineraries by country, number of days or keywords (e.g. "fjords", "Alps", "coast", a town). Returns matching trips with days, km and a link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_road_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the user, for the links (en, de, es, fr, it, cs, da, sv, nb, pl, nl). Default en.
limitNoDefault 8.
queryNoFree-text keywords: a place, region, landscape or theme.
countryNoCountry name or ISO code, e.g. "Norway" or "NO".
max_daysNoLongest trip wanted, in days.
min_daysNoShortest trip wanted, in days.
travel_dateNoWhen the user will drive (YYYY-MM-DD), to check seasonal passes. Default today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / max_days / description
      Added value: +"Longest trip wanted, in days."
    • addedInput schema / properties / min_days / description
      Added value: +"Shortest trip wanted, in days."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds real behavioral value by disclosing the shape of results (days, km, link), which matters because there is no output schema; it omits empty-result behavior and whether filters combine with AND semantics.

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?

Two sentences, no waste: the search scope and filter axes come first, the return payload second. Nothing is repeated from the schema or annotations.

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?

For a seven-parameter, all-optional, read-only search with no output schema, the description covers purpose, filters and return fields adequately. Minor gaps remain around combining filters and zero-match behavior, but no essential calling information is missing.

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 would be 3, but the description adds meaning: it gives concrete query keyword examples ('fjords', 'Alps', 'coast') and signals that a town name is acceptable free text, which the schema's abstract 'place, region, landscape or theme' does not make as obvious.

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?

States a specific verb and resource ('Search Roadcut's European road trip itineraries') plus the three filter axes (country, days, keywords) and what comes back (days, km, link). It is clearly a multi-result search, which implicitly separates it from the singular get_road_trip sibling, though no sibling is named explicitly.

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 the filter list: the agent can infer this is for browsing trips by country, duration or theme. There is no explicit statement of when to prefer this over get_road_trip for a single itinerary, nor any exclusion such as non-European trips.

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