GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

compute_ndvi

Compute Normalized Difference Vegetation Index (NDVI) from a raster by specifying red and near-infrared band indices and save the result as a GeoTIFF file.

Instructions

Compute NDVI (Normalized Difference Vegetation Index) and save to GeoTIFF.

Parameters:

source: input raster path.
red_band_index: index of red band (1-based).
nir_band_index: index of near-infrared band (1-based).
destination: output NDVI raster path.

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": {
      "source": "<source>",
      "red_band_index": "<red_band_index>",
      "nir_band_index": "<nir_band_index>",
      "destination": "<destination>"
    },
    "name": "compute_ndvi"
  }
}

Input Schema

Name	Required	Description	Default
`source`	Yes
`red_band_index`	Yes
`nir_band_index`	Yes
`destination`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / destination / title
```
Removed value: -"Destination"
```
- removedInput schema / properties / nir_band_index / title
```
Removed value: -"Nir Band Index"
```
- removedInput schema / properties / red_band_index / title
```
Removed value: -"Red Band Index"
```
- removedInput schema / properties / source / title
```
Removed value: -"Source"
```
- removedInput schema / title
```
Removed value: -"compute_ndviArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states a read-compute-write operation but does not mention file overwrite behavior, required CRS, or potential side effects, leaving significant gaps.

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?

The description is extremely concise: one sentence for purpose and a clear bullet list for parameters. Every part serves a purpose, no wasted words, and well-structured for quick scanning.

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?

The tool is simple with 4 parameters and an output schema, so the description covers basics. However, it lacks behavioral context (e.g., overwrite, errors) and usage guidance, making it minimally adequate for a standalone read.

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?

With 0% schema coverage, the description adds crucial meaning: clarifying that band indices are 1-based and that destination is an output path. This compensates well for the schema's lack of descriptions, though more formatting details would improve it.

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?

The description clearly states the tool computes NDVI and saves to GeoTIFF, using a specific verb ('Compute') and resource (NDVI). However, it does not differentiate from similar tools like raster_algebra, which could also compute indices, lacking sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like raster_algebra or concat_bands. It implies basic usage but offers no context for selection among many similar raster tools.

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

Deploy Server