GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

focal_statistics

Compute focal (moving window) statistics on a raster to analyze local neighborhood values. Select from mean, min, max, or standard deviation and specify an odd window size.

Instructions

Compute focal (moving window) statistics on a raster. Args: raster_path: Path to the input raster. statistic: Statistic to compute ('mean', 'min', 'max', 'std'). size: Window size (odd integer). output_path: Optional path to save the result. Returns: Dictionary with status, message, and output path if saved.

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>",
      "statistic": "<statistic>"
    },
    "name": "focal_statistics"
  }
}

Input Schema

Name	Required	Description	Default
`raster_path`	Yes
`statistic`	Yes
`size`	No
`output_path`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.0.0Jan 2, 2026
- addedInput schema / properties / output_path / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / output_path / title
```
Removed value: -"Output Path"
```
- removedInput schema / properties / output_path / type
```
Removed value: -"string"
```
- removedInput schema / properties / raster_path / title
```
Removed value: -"Raster Path"
```
- removedInput schema / properties / size / title
```
Removed value: -"Size"
```
- removedInput schema / properties / statistic / title
```
Removed value: -"Statistic"
```
- removedInput schema / title
```
Removed value: -"focal_statisticsArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It mentions inputs and return dictionary but does not disclose side effects, read-only nature, or potential destructive actions beyond writing an output file.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise but uses a verbose docstring format with Args and Returns. It could be more compact while retaining clarity.

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 the simple tool nature and the mention of return dictionary (status, message, output path), the description is complete enough for basic usage, though it lacks edge cases.

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 coverage is 0%, but the description adds meaning: explains raster_path, statistic (with options), size (odd integer), and output_path (optional). This adds value beyond the schema alone.

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 verb 'Compute' and the resource 'focal (moving window) statistics on a raster', which distinguishes it from sibling tools like zonal_statistics.

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 on when to use this tool versus alternatives such as raster_algebra or zonal_statistics, nor any mention of when not to use it.

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

Deploy Server