rf-los-mcp

Overview Schema Source Related Servers Discussions Admin

Dem Cache Status

dem_cache_status

Lists locally cached terrain tiles with names and sizes, plus the cache directory, so you can verify offline DEM data available for line-of-sight checks.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dem_cache_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tiles`	Yes
`cache_dir`	Yes
`tile_count`	Yes
`total_bytes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It makes clear this is a local, non-mutating listing that includes the cache directory, and it explains the tile naming scheme so returned names can be interpreted. It does not say what happens when the cache directory is absent or empty, whether results are ordered, or whether any size/limit applies.

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?

Two short sentences, front-loaded with what the tool returns, and the second sentence is a compact decoding key for the tile names. No filler, no repetition of the title.

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?

For a zero-parameter read tool with an output schema and no annotations, this is nearly sufficient: the return shape is covered by the schema and the naming convention is explained in prose. The remaining gap is edge-case behavior for a missing or empty cache directory, which an agent would likely want to know before treating an empty result as an error.

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?

The tool takes no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description spends its words on output interpretation (the south-west corner naming convention, e.g. S34E151 spanning -34 to -33 latitude and 151 to 152 longitude), which is genuinely additive rather than redundant.

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 states a specific verb and resource: 'List the terrain tiles cached locally (name, bytes) and the cache directory.' It also names the exact fields returned, which lets an agent distinguish this inspection tool from the sibling tools that compute or fetch data (terrain_elevation, dem_prefetch, rf_los_check).

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?

There is no explicit when-to-use guidance, no mention of an alternative, and no statement of what this tool should be used for versus dem_prefetch. The use case (checking cache contents, presumably before or after prefetching) is only implied by the name and the listing semantics rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server