Skip to main content
Glama
Sign In
rf-los-mcp

rf-los-mcp

by aaronjbrown
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Terrain Elevation

terrain_elevation

Retrieves bare-earth ground elevation in metres above mean sea level for up to 1,000 coordinate points, supporting RF line-of-sight and terrain profile analysis.

Instructions

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.

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": {
      "points": "<points>"
    },
    "name": "terrain_elevation"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes

Output Schema

NameRequiredDescriptionDefault
pointsYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does so well: it warns that sea and uncovered areas silently return 0 (a critical false-zero gotcha), that missing tiles are fetched on demand at ~12 MB per 1-degree square with a 16-tile cap per call, and that failures raise an error naming the tile. Those are exactly the side effects and failure modes an agent needs before invoking it.

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?

Four short sentences, each carrying distinct information: what it measures, the input limit, the zero-value caveat, and the tile-download cost/failure behaviour. The most consequential caveat (sea reads as 0) is placed early and nothing is redundant.

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

Completeness5/5

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

For a single-parameter lookup tool with an output schema available, the description covers dataset provenance, units, input constraints, silent-zero behaviour, network download cost, and error semantics. No gap remains that would cause a misinformed call.

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 description coverage is 0%, so the description must compensate, and it adds the coordinate format ('decimal degrees') and the cardinality limit ('up to 1000 points') that the JSON schema does not express. The lat/lon structure itself is already fully specified by the schema with min/max bounds.

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?

The description names the exact quantity returned ('ground elevation in metres above mean sea level'), the source dataset and processing level ('FABDEM, bare earth'), which tells an agent precisely what this tool answers. It also points at dem_prefetch for the tile-management sibling, so the boundary with at least one neighbour is explicit.

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?

It gives a clear usage context (batch point queries, up to 1000 points in decimal degrees) and routes tile-related work to dem_prefetch with 'see dem_prefetch'. It does not state when to prefer terrain_profile over this tool for continuous paths, so the exclusions are only partially covered.

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