Skip to main content
Glama
rf-los-mcp

rf-los-mcp

by aaronjbrown

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
XDG_CACHE_HOMENoBase cache directory used for terrain tiles when RF_LOS_CACHE_DIR is not set (falls back to ~/.cache/rf-los).
RF_LOS_CACHE_DIRNoDirectory where terrain tiles are cached. Tiles are cached in $RF_LOS_CACHE_DIR, else $XDG_CACHE_HOME/rf-los, else ~/.cache/rf-los.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
rf_los_checkA

Check RF line of sight between observer A and target B over FABDEM terrain.

A is the observer (default 1.5 m above ground level); B is the target, e.g. a repeater (default 25.0 m AGL). Coordinates are decimal degrees, heights are metres. a_height_ref/b_height_ref are "agl" (above ground level, the default) or "amsl" (above mean sea level).

There is NO default frequency. Without frequency_mhz the check is geometric only (mode="geometric", no Fresnel zone) and the result says so. With frequency_mhz the 0.6 x first Fresnel zone must be clear for a "clear" verdict (mode="rf"); partial intrusion is "marginal". Take repeater lat/lon and output frequency (MHz) from the repeaterbook tools.

k_factor is the effective earth radius factor (default 4/3, standard atmosphere). snap_radius_m (default 1000 m, max 10000, 0 disables) snaps the TARGET B (not the observer A) to the highest nearby ground within that radius, since repeater coordinates are often imprecise (valley town vs the hilltop site); the move is reported in target_snap. A and B must be different points at most 300 km apart. Vegetation and buildings are not modelled (bare-earth DEM). The first query in a new area downloads a ~12 MB terrain tile per 1 degree square, which can take about a minute; use dem_prefetch to pre-download. One call downloads at most 16 new tiles.

rf_los_routeA

Assess RF coverage of target repeaters along a route (e.g. a drive or hike).

Provide the route as EXACTLY ONE of waypoints (list of lat/lon, in order), gpx_path (path to a .gpx file of at most 10 MB readable by this server, ~ expanded; track points, else route points, else waypoints) or geojson_path (path to a .geojson/.json file of at most 10 MB, e.g. an OpenStreetMap export; prefer this over copying GeoJSON coordinates into waypoints, which risks swapping GeoJSON's [lon, lat] order). The file must be valid RFC 7946 GeoJSON (checked against the GeoJSON JSON Schema; other JSON is rejected). GeoJSON LineString/MultiLineString pieces are joined end to end (branching or disconnected pieces are an error); Point features with a name property become named waypoints placed on the line (within 500 m); with no lines, the Points are the route. The route must have non-zero length. Each target has lat, lon, optional name, height_m (default 25.0 m AGL), height_ref ("agl" or "amsl"), and optional per-target frequency_mhz / snap_radius_m which override the call-level values.

Waypoints / GPX points are route GEOMETRY: the route is resampled every sample_spacing_m metres (default 200) along its length, so dense GPS tracks are fine. Per-waypoint verdicts are reported ONLY for NAMED waypoints plus the first ("Start") and last ("End") point: give a name to each stop you want a result for (summit, hut, camp). GPX track points are unnamed geometry; GPX route points and waypoints keep their names. Line of sight is evaluated at the samples, an approximation that can miss narrow ridges between them. At most 10000 line-of-sight checks (samples x targets) per call; for long routes or many targets increase sample_spacing_m.

observer_height_m is the antenna height AGL along the route (default 1.5 m). Route positions are in km. Targets farther than max_range_km (default 100, max 300) from a point are reported out_of_range.

There is NO default frequency: without frequency_mhz the result is geometric only (no Fresnel zone) and says so. Take repeater lat/lon and output frequency (MHz) from the repeaterbook tools. Snapping (snap_radius_m, default 1000 m, 0 disables) moves the TARGETS to higher nearby ground, never the observer waypoints.

For an out-and-back route pass the OUTBOUND LEG ONLY: the return leg repeats the same coverage. Output has per-target coverage segments with percent clear/marginal, verdicts at Start/End and named waypoints, and coverage gaps. Vegetation is not modelled. A first query in a new area downloads ~12 MB per 1 degree terrain tile (about a minute each; at most 16 new tiles per call); use dem_prefetch. At most 50 targets per call, and at most 5,000,000 terrain samples in total (target snapping included).

terrain_elevationA

Ground elevation in metres above mean sea level (FABDEM, bare earth).

Up to 1000 points (decimal degrees). Sea and areas not in the dataset read as 0. Missing land tiles are downloaded on demand (~12 MB per 1 degree square, at most 16 new tiles per call) or raise an error naming the tile; see dem_prefetch.

terrain_profileA

Elevation profile (metres AMSL) along a path through 2 or more points.

Samples every spacing_m metres (default 30) along great-circle segments between the points; every input point is a sample. Returns distance in metres from the start, lat/lon and elevation per sample. With include_curvature=true each sample also has curvature_adjusted_m = elevation + d1d2/(2k*R), the terrain as seen against the straight first-to-last chord, with earth bulge for k_factor (default 4/3). At most 20000 samples; for longer paths increase spacing_m. At most 16 new terrain tiles are downloaded per call.

dem_cache_statusA

List the terrain tiles cached locally (name, bytes) and the cache directory.

Tiles are named by their south-west corner, e.g. S34E151 covers latitude -34 to -33 and longitude 151 to 152.

dem_prefetchA

Download terrain tiles for an area so later queries work offline.

Give EITHER a bounding box (south, west, north, east; decimal degrees) OR center_lat, center_lon and radius_km. Each 1 degree tile is about 12 MB and can take about a minute to download. If the area needs more than max_tiles (default 16, at most 100) tiles, nothing is downloaded and an error states the count; raise max_tiles deliberately. Tiles that fail to download are listed in failed (retry later); ocean tiles need no data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a clearly distinct operation: point-to-point LOS (rf_los_check) vs route coverage (rf_los_route), point elevations (terrain_elevation) vs path profiles (terrain_profile), and cache inspection (dem_cache_status) vs tile download (dem_prefetch). The descriptions explicitly cross-reference each other (e.g. 'use dem_prefetch to pre-download', 'prefer this over copying GeoJSON'), which further reduces misselection risk.

Naming Consistency4/5

All names are snake_case and grouped by domain prefix (rf_los_*, terrain_*, dem_*), which is highly predictable. The only minor inconsistency is that most names are noun-phrase labels while dem_prefetch leads with a verb, but the overall pattern is still readable and coherent.

Tool Count5/5

Six tools is well-scoped for an RF line-of-sight plus DEM server: two analysis tools, two terrain-data tools, and two cache-management tools. Every tool earns its place, with no redundant or filler entries.

Completeness4/5

The surface covers the core lifecycle: terrain data acquisition (dem_prefetch), inspection (dem_cache_status), elevation queries, profiles, and both point-to-point and route LOS analysis. Minor gaps exist, such as no fan-out check of multiple targets from a single fixed observer, no way to clear/purge cached tiles, and no direct link-budget or best-repeater recommendation, but agents can work around these by looping calls.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues