Skip to main content
Glama

Roadcut — European road trips

Mountain pass season

get_mountain_pass
Read-onlyIdempotent

When a European mountain pass (Alps, Norway, Carpathians…) usually opens and closes, whether it opened this year, night closures, and where the road operator publishes live status. Search by pass name or country; with neither, every pass Roadcut tracks is listed. Seasons are records of past years, not live status; each result links to the operator's live status.

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": "get_mountain_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the user, for the links (en, de, es, fr, it, cs, da, sv, nb, pl, nl). Default en.
nameNoPass name or part of it, e.g. "Trollstigen", "Stelvio".
countryNoCountry name or ISO code.
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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: results are historical season records rather than current conditions, each result carries an operator live-status link, and an unfiltered call returns the full catalogue. It is silent on pagination or result-size limits for the unfiltered listing, which is the main remaining gap.

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?

Three tight sentences, front-loaded with what the tool answers, followed by how to query it and the critical caveat about historical vs. live data. The 'Alps, Norway, Carpathians…' parenthetical earns its place by scoping the geography, and there is no filler.

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?

With no output schema, the description carries the burden of describing returns and does so adequately: season records per pass plus a link to the operator's live status. What is missing is the shape of a result record and any note on how travel_date defaults or affects filtering, which leaves a small gap for a four-parameter lookup tool.

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 four parameters (lang, name, country, travel_date) are already documented at the field level, which sets the baseline at 3. The description adds one thing the schema cannot express — that name and country are independently optional and omitting both yields the complete list — but it never mentions travel_date or how it interacts with the 'opened this year' framing, so the added value is modest.

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 resource (European mountain passes) and enumerates exactly what is returned: seasonal open/close windows, whether it opened this year, night closures, and the operator's live-status URL. That scope is distinct from the sibling tools (find_road_trips, get_road_trip, get_driving_rules), so an agent can route to it 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 gives concrete usage guidance: search by pass name or country, and with neither the tool lists every tracked pass, so the agent knows the zero-argument call is valid and broad. It also draws a clear boundary — seasons are historical records, not live status, and live status comes from the linked operator page — but it does not name any alternative tool or state when a different sibling should be preferred.

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