GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

reclassify_raster

Reclassify raster values by mapping old cell values to new ones using a dictionary, for custom recoding in geospatial analysis.

Instructions

Reclassify raster values using a mapping dictionary. Args: raster_path: Path to the input raster. reclass_map: Dictionary mapping old values to new values (e.g., {1: 10, 2: 20}). output_path: Path to save the reclassified raster. Returns: Dictionary with status and message.

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": {
      "raster_path": "<raster_path>",
      "reclass_map": "<reclass_map>",
      "output_path": "<output_path>"
    },
    "name": "reclassify_raster"
  }
}

Input Schema

Name	Required	Description	Default
`raster_path`	Yes
`reclass_map`	Yes
`output_path`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / output_path / title
```
Removed value: -"Output Path"
```
- removedInput schema / properties / raster_path / title
```
Removed value: -"Raster Path"
```
- removedInput schema / properties / reclass_map / title
```
Removed value: -"Reclass Map"
```
- removedInput schema / title
```
Removed value: -"reclassify_rasterArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior. It states output is saved to output_path and returns a dict with status/message, but lacks details on error handling, overwrite behavior, or performance implications. It does not contradict any annotations (none provided).

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 brief and well-structured in a standard docstring format with Args and Returns sections. Every sentence is informative, and the purpose is front-loaded with no redundant words.

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 description covers the basic purpose and parameters but lacks output schema details (e.g., exact keys in the returned dict) and constraints on the mapping dictionary. Given simplicity, it is adequate but not thorough.

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 description adds meaning beyond the schema by explaining each parameter: raster_path (input path), reclass_map (mapping dict with example), output_path (save location). Schema coverage is 0%, so this is essential. It could be strengthened by specifying numeric key/value constraints.

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 clearly states the tool's action ('Reclassify raster values') and the method ('using a mapping dictionary'). It distinguishes itself from sibling tools like clip_raster_with_shapefile or raster_algebra by specifying reclassification with a mapping.

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?

No guidance is provided on when to use this tool vs alternatives, such as raster_algebra or resample_raster. There is no mention of prerequisites, data type constraints, or scenarios where this tool is inappropriate.

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

Deploy Server