Hutlists — Alpine huts

Search Huts Tool

search-huts

Read-onlyIdempotent

Search Alpine mountain huts by country, region, name, access difficulty, minimum elevation or proximity to a point. Returns a page of hut summaries with slugs for get-hut.

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": "search-huts"
  }
}

Input Schema

Name	Required	Description
`q`	No	Free-text match on the hut name.
`near`	No	"latitude,longitude" to search around, e.g. "46.02,7.75".
`page`	No	Page number, from 1.
`sort`	No	Sort order.
`region`	No	Region slug from list-regions, e.g. "tyrol".
`country`	No	Country slug from list-regions, e.g. "austria".
`per_page`	No	Results per page (max 100).
`radius_km`	No	Radius around `near` in km (default 25, max 200).
`difficulty`	No	Access difficulty.
`min_elevation`	No	Minimum elevation in metres.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description does not need to repeat those. It adds value by stating the return format (page of hut summaries with slugs), which is behavioral context beyond the annotations. It does not contradict annotations and provides useful output details.

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 a single, efficient sentence that front-loads the primary purpose and mentions the key output. There is no redundancy or wasted words; every clause adds information.

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 10 parameters and no output schema, the description adequately summarizes the tool's function and mentions the output format (slugs for get-hut). It relies on the schema for parameter details, which is acceptable given 100% coverage. It covers the essentials without over-explaining.

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 parameters are already documented in the input schema. The description adds no extra parameter-level semantics beyond the generic list of filters, which the schema already conveys. Baseline 3 is appropriate for high schema coverage.

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 states a specific action (Search Alpine mountain huts) with a clear resource and lists the filter dimensions (country, region, name, difficulty, elevation, proximity). It also mentions the output (page of hut summaries with slugs for get-hut), distinguishing it from siblings like get-hut and list-regions.

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 implies a usage flow by noting that results include slugs for get-hut, suggesting this is the search step before retrieving details. However, it does not explicitly state when to use this versus alternatives or mention exclusions. The implication is clear but not explicit, so a 4 is appropriate.

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

All Hutlists — Alpine huts tools Inspect

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

Need Help?