Skip to main content
Glama

get_trail_closures_nearby

Read-onlyIdempotent

Find hiking trail closures and detours within a set radius of a WGS84 point so you can plan around affected routes.

Instructions

Hiking trail closures and detours near a WGS84 point

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

Input Schema

NameRequiredDescriptionDefault
latYesLatitude (WGS84)
lonYesLongitude (WGS84)
radiusNoMetres, max 50000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude in WGS84 (e.g. 46.9480 for Bern)."New value: +"Latitude (WGS84)"
    • changedInput schema / properties / lon / description
      Previous value: -"Longitude in WGS84 (e.g. 7.4474 for Bern)."New value: +"Longitude (WGS84)"
    • addedInput schema / properties / radius / default
      Added value: +10000
    • changedInput schema / properties / radius / description
      Previous value: -"Search radius in metres. Default: 10000 (10 km). Max: 50000."New value: +"Metres, max 50000"
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered without the description. The description adds only the domain fact that results are hiking closures/detours; it says nothing about result volume, radius behavior, or whether an empty result is possible near the 50 km cap.

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 nine-word fragment with zero padding and the spatial qualifier front-loaded. It is under-specified rather than bloated, so conciseness is not the failing dimension.

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 three-parameter read tool with an output-free contract, the definition is minimally sufficient — the agent can call it correctly. It is incomplete in that it does not explain the relationship to get_trail_closures or what a result entry contains (closure reason, detour, geometry).

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% and every parameter carries its own description including units and the max radius, so the schema does the work. 'Near a WGS84 point' reinforces that lat/lon are coordinates rather than place names, but adds no detail beyond the schema.

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?

Names a specific resource (hiking trail closures and detours) plus a spatial scope (near a WGS84 point), which is concrete and searchable. It fails to distinguish itself from the sibling get_trail_closures, leaving the agent to infer the difference between the list-all and the proximity variants.

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 spatial framing ('near a point') implies the usage context — proximity queries — but there is no explicit when-to-use guidance and no pointer to get_trail_closures as the alternative for non-spatial lookups. The agent must infer the split from the name alone.

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