Skip to main content
Glama

Hiking trail closures near a point

get_trail_closures
Read-only

Retrieve current official hiking-trail closures and detours around a WGS84 point before recommending a hike. Search covers a configurable radius, helping you avoid blocked routes.

Instructions

Current official hiking-trail closures and detours near a WGS84 point. The search covers roughly radius_km (default 20 km, max 100 km) around the point; it is a map-tolerance buffer that may be a square box, so features up to ~1.4× radius_km away can be included, and distances are not computed. There is no nationwide listing. Use before recommending any hike.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_trail_closures"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude
lonYesWGS84 longitude
limitNo
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond by disclosing that the radius is a map-tolerance buffer that may be a square box, that features up to ~1.4× radius_km can leak in, that distances are not computed, and that results are current/official rather than historical. These are exactly the non-obvious traits an agent needs to interpret results correctly.

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 dense sentences with the resource definition front-loaded, followed by the spatial caveat and the usage rule. Every clause carries operational information — the 1.4× and 'distances are not computed' details directly prevent misinterpretation of results.

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 conveys what is returned conceptually (closures and detours), but does not say what fields a record holds or whether detour information is structured. The lat/lon bounds restriction in the schema (a limited region) is also unmentioned, though the schema itself carries it.

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 50% (lat/lon documented, limit and radius_km not), and the description compensates strongly for radius_km by giving its default, maximum, and true buffer semantics. The limit parameter receives no explanation anywhere, leaving one gap.

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?

States a specific verb and resource — 'Current official hiking-trail closures and detours' — plus the spatial scope ('near a WGS84 point'). No sibling in the catalog covers trail closures, so the tool is unambiguous without needing an explicit differentiation sentence.

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?

'Use before recommending any hike' gives explicit timing guidance, and 'There is no nationwide listing' tells the agent it must supply a point rather than attempt a broad query. It stops short of naming an alternative fallback tool or exclusion cases, so it is clear but not fully routing.

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