Skip to main content
Glama

Hüttentouren

by org.huettentouren
OverviewDiscussionsAdmin

Server Details

Hut-to-hut hiking tours in the Alps with live availability from multiple booking systems.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
99.9% over 37 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool serves a distinct purpose: fetch retrieves details for a single tour, recommend_tours provides recommendations based on availability, and search allows searching by fields. No overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (fetch, recommend_tours, search) using lowercase with underscores for multi-word names.

Tool Count4/5

Three tools is slightly low but appropriate for a focused domain of hut-to-hut tours. The set covers core read operations without extraneous tools.

Completeness3/5

The surface covers fetching, searching, and recommending, but lacks any write or interactive tools (e.g., booking, rating). For a read-only catalog, it may be sufficient, but gaps exist for full lifecycle.

Available Tools

3 tools
fetchFetch compact tour detailsA
Read-only
Inspect

Fetch compact, curated details for one published hut-to-hut tour. The returned url is the canonical huettentouren.org detail page — link users there.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesRoute id returned by search or recommend_tours.

Output Schema

ParametersJSON Schema
NameRequiredDescription
tourYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by noting the returned details are 'compact' and 'curated', and that the url should be used for the canonical page, which informs the agent about the nature of the output and expected user action. No contradiction with annotations.

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 concise sentences with zero superfluous words. Every sentence serves a purpose: stating the action and providing guidance on using the result. The description is front-loaded with the primary purpose.

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

Completeness5/5

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

Given the simplicity (1 required parameter, no nested objects, presence of output schema), the description is complete. It covers what the tool does, what the input is, and how to use the output (direct users to the url). No further explanation of return values is needed due to output schema.

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% with the id parameter described as 'Route id returned by search or recommend_tours.' The tool description doesn't repeat that but indirectly reinforces it by mentioning the tool fetches 'one published hut-to-hut tour.' This adds contextual meaning beyond the schema, justifying a score above baseline 3.

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 clearly states the tool fetches 'compact, curated details for one published hut-to-hut tour', using a specific verb and resource. It distinguishes from sibling tools (recommend_tours, search) which return lists or recommendations, while this returns details for a single tour.

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?

The description explains that the returned 'url' is canonical and should be linked to users, providing clear post-invocation guidance. The input schema's parameter description explicitly ties the id to results from search or recommend_tours, indicating when to use this tool. Though it doesn't state when not to use, the context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

recommend_toursRecommend hut-to-hut toursA
Read-only
Inspect

Recommend fitting hut-to-hut tours using structured tour data and fresh availability rules. Each result includes url, the canonical huettentouren.org detail page — link users there, not to any upstream source.

ParametersJSON Schema
NameRequiredDescriptionDefault
toNoPreferred end date in YYYY-MM-DD format.
fromNoPreferred start date in YYYY-MM-DD format.
monthsNoPreferred months in YYYY-MM format.
peopleNoNumber of people in the group.
privacyNoPrivacy controls for non-blocking preference insight capture.
transportNoPreferred access mode.
maxResultsNoMaximum number of results to return.
difficultiesNoAllowed tour difficulty labels.
durationMaxDaysNoMaximum tour duration in days.
durationMinDaysNoMinimum tour duration in days.

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultsYes
warningsYes
reasonCodesYes
resultStatusYes
noMatchReasonYes
freshnessPolicyYes
normalizedInputYes
degradationFlagsYes
recommendedRouteIdsYes

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context by mentioning 'fresh availability rules' and the canonical URL requirement, which goes beyond what annotations provide.

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?

The description is two sentences long, front-loaded with the core purpose, and contains no redundant words. Every sentence adds value.

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?

Given the tool's complexity (10 parameters, nested objects) and the presence of an output schema (not shown but indicated), the description covers the essential purpose and output format. It is complete enough for an agent to understand the tool's role.

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 coverage is 100%, so each parameter is documented. The description does not add new semantic meaning beyond the schema, but it provides high-level context about how parameters are used (e.g., structured data, availability rules). Baseline 3 is appropriate.

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 clearly states it recommends hut-to-hut tours using structured data and availability rules. It distinguishes itself from sibling tools 'fetch' and 'search' by specifying the focus on recommendations and linking to canonical pages.

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?

The description implies usage for recommending tours based on preferences, but it does not explicitly contrast with alternatives like 'search' or 'fetch'. No when-to-use or when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedrecommend_tours2 fields changed
      • addedOutput schema / properties / results / items / properties / url
        Added value: +{
+  "description": "Canonical huettentouren.org detail page. Use this when linking users to the tour.",
+  "format": "uri",
+  "type": "string"
+}
      • changedOutput schema / properties / results / items / required
        Previous value: -[
-  "routeId",
-  "name",
-  "region",
-  "status",
-  "score",
-  "reasons",
-  "sampleStartDates",
-  "availability"
-]New value: +[
+  "routeId",
+  "name",
+  "region",
+  "url",
+  "status",
+  "score",
+  "reasons",
+  "sampleStartDates",
+  "availability"
+]
    • Changedsearch2 fields changed
      • addedOutput schema / properties / results / items / properties / url
        Added value: +{
+  "description": "Canonical huettentouren.org detail page. Use this when linking users to the tour.",
+  "format": "uri",
+  "type": "string"
+}
      • changedOutput schema / properties / results / items / required
        Previous value: -[
-  "id",
-  "name",
-  "region",
-  "difficulty",
-  "durationDays"
-]New value: +[
+  "id",
+  "name",
+  "region",
+  "url",
+  "difficulty",
+  "durationDays"
+]
  2. 3 tool updates
    • First observedfetch
    • First observedrecommend_tours
    • First observedsearch

Related MCP Connectors

Related MCP Servers

  • hut-reservation-mcp

    domwoe
    A
    license
    A
    quality
    D
    maintenance
    Enables searching SAC huts, checking availability, and preparing booking or cancellation handoffs on hut-reservation.org with a safety model for writes.
    10
    11 npm
    3
    MIT

  • bergauf

    lailo
    F
    license
    Not graded
    quality
    D
    maintenance
    Lets an LLM plan hikes anywhere in Switzerland by combining named routes, elevation profiles, weather forecasts, and public transport.
    7
    -

  • hike-finder

    BoykoNeov
    A
    license
    A
    quality
    A
    maintenance
    Finds marked hiking routes from OpenStreetMap filtered by locally-computed elevation gain, distance, loop shape, and car/chairlift access, providing consistent and tunable metrics instead of third-party scraped data.
    1
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources