Skip to main content
Glama

Route on mountain

route_on_mountain
Read-onlyIdempotent

Route between named pistes, lifts, the resort base or latitude,longitude coordinates using mapped OSM pistes and lifts. Names match accent-insensitively and partially (exact, then prefix, then contained words); a piste or lift split into several connected OSM pieces counts as one. A lift used as from resolves to its top station, where you ski away; a lift used as to resolves to its bottom station, unless coordinates say otherwise. Ambiguous names return candidates. Coordinates more than 5 km from the resort are rejected. Easy, intermediate and advanced avoid terrain above that level; only expert permits expert, freeride and extreme terrain.

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": {
      "resort": "<resort>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "route_on_mountain"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
levelNo
resortYesResort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)
avoid_closedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / resort / description
      Added value: +"Resort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond them: the exact→prefix→contained matching ladder, multi-piece OSM piste consolidation, asymmetric lift station resolution, candidate returns on ambiguity, the 5 km coordinate rejection rule, and what each difficulty level excludes. This is exactly the added context the dimension rewards.

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 text is dense but every sentence carries operational information — matching rules, lift resolution, ambiguity, coordinate limits, level semantics — with no filler. It is a single undifferentiated block rather than being grouped by parameter, which slightly hurts scannability but not economy.

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 does what it can by noting that ambiguous names return candidates, and it covers the three required parameters plus the level enum thoroughly. The remaining gaps are 'avoid_closed' behavior and the shape of a successful route response (distance, segments, geometry), which an agent would still have to discover by calling.

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 only 20%, with just the 'resort' parameter documented, so the description has to compensate and largely does — it explains that 'from'/'to' accept piste names, lift names, the resort base, or coordinates, and defines the level enum's terrain-exclusion semantics. The 'avoid_closed' parameter is never addressed, leaving one defaulted flag unexplained.

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 opens with a specific verb and resource ('Route between named pistes, lifts, the resort base or latitude,longitude coordinates using mapped OSM pistes and lifts'), naming the exact input types and data source. No sibling tool performs routing, and the definition makes that scope unmistakable without requiring the schema to be opened.

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 clear operational guidance for how to use the tool: names may be partial or accent-insensitive, lifts resolve to top/bottom stations depending on direction, and out-of-resort coordinates are rejected. It does not name alternatives or explicitly state when not to use it, but for a routing tool with no functional sibling that gap is minor.

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