Skip to main content
Glama
rf-los-mcp

rf-los-mcp

by aaronjbrown

Related Servers

Alternatives to rf-los-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to retrieve ground elevations worldwide, profile route ascent/descent and grades, sample grid areas for high/low points and relief, and test whether terrain blocks a sightline, drawing on USGS 3DEP and Open Topo Data with per-value provenance.
      351 npm
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying global and regional DEM datasets for point and batch elevations, neighbourhood elevation and slope statistics, charts, composite terrain maps, and 3D perspective surfaces through a local bridge to the hosted Geospatial System location-profile MCP server.
      70 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables geocoding, reverse geocoding, elevation profiles, static map PNGs, and coordinate reprojection using MapTiler's OpenStreetMap data.
      85 npm
      MIT

    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