GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

reproject_raster

Reproject a raster dataset to a specified target CRS (e.g., EPSG:4326) with customizable resampling method, saving the result to a local path.

Instructions

Reproject a raster dataset to a new CRS and save the result.

Parameters:

source: local path or HTTPS URL of the source raster.
target_crs: target CRS string (e.g., "EPSG:4326").
destination: local filesystem path for the reprojected raster.
resampling: resampling method: "nearest", "bilinear", "cubic", etc.

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>",
      "target_crs": "<target_crs>",
      "destination": "<destination>"
    },
    "name": "reproject_raster"
  }
}

Input Schema

Name	Required	Default
`source`	Yes
`target_crs`	Yes
`destination`	Yes
`resampling`	No	nearest

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 / resampling / title
```
Removed value: -"Resampling"
```
- removedInput schema / properties / source / title
```
Removed value: -"Source"
```
- removedInput schema / properties / target_crs / title
```
Removed value: -"Target Crs"
```
- removedInput schema / title
```
Removed value: -"reproject_rasterArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool saves to a destination path, but does not mention potential side effects (e.g., overwriting files), performance considerations, or supported CRS formats beyond EPSG example. For a simple operation it is adequate but not detailed.

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 short and to the point, with a clear initial sentence stating the purpose followed by a compact parameter list. No unnecessary words or repetition.

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?

Given 4 parameters, no annotations, and the presence of an output schema (which relieves the description from explaining return values), the description is fairly complete. It covers purpose, parameter explanations, and expected behavior. Missing minor details like error handling, but still informative.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must explain parameters. It does so effectively: source includes local path or HTTPS URL, target_crs shows example format, destination is local path, and resampling lists example methods. This adds significant clarity beyond the schema's type hints and default.

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 reprojects a raster dataset to a new CRS and saves the result. It uses a specific verb ('Reproject') and resource ('raster dataset'), differentiating it from siblings like clip_raster_with_shapefile or resample_raster.

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 alternative transformation tools (e.g., resample_raster for change in resolution). It lacks explicit context for when-to-use, when-not-to-use, or suggestions for alternatives.

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

Deploy Server