Skip to main content
Glama

get_trail_closures

Read-onlyIdempotent

Retrieve current Swiss hiking trail closures and detours from ASTRA/Schweizer Wanderwege data, with optional filters for closure type, reason, and result limit.

Instructions

Current hiking trail closures and detours (ASTRA/Schweizer Wanderwege)

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_trail_closures"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOmit for both
limitNomax 100
reasonNoPartial match, e.g. Steinschlag, Bauarbeiten, Hangrutsch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return. Default: 20. Max: 100."New value: +"max 100"
    • changedInput schema / properties / reason / description
      Previous value: -"Optional search term for closure reason (e.g. 'Steinschlag', 'Bauarbeiten', 'Hangrutsch', 'Hochwasser'). Matches against the reason field (German or English). Case-insensitive partial match."New value: +"Partial match, e.g. Steinschlag, Bauarbeiten, Hangrutsch"
    • changedInput schema / properties / type / description
      Previous value: -"Optional: filter by type — 'closure' (Sperrung) or 'detour' (Umleitung). If omitted, returns both."New value: +"Omit for both"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only the data provenance and the 'current' freshness signal; it says nothing about result volume, sorting, or how stale the upstream feed may be.

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?

A single front-loaded noun phrase with no filler; nothing needs trimming. It is terse to the point of omitting scope, but the wording itself is efficient.

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

Completeness3/5

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

For a simple, fully-documented, annotation-covered read tool this is close to sufficient, but an agent still lacks the geographic scope and the distinction from get_trail_closures_nearby. No output schema exists, so a hint about the returned fields would have helped.

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%, with enum, default and example values already documented for type, limit and reason. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

The description names a specific resource — current hiking trail closures and detours — and attributes the data sources (ASTRA/Schweizer Wanderwege), so an agent knows what it returns. It stops short of differentiating from the sibling get_trail_closures_nearby, leaving the national-vs-local scope ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of the closely related get_trail_closures_nearby tool, which is the most likely source of mis-selection. The agent must infer from the name alone that this is the unfiltered/national variant.

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

Deploy Server

Other Tools