GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

moran_local

Detect spatial clusters and outliers using Local Moran's I. Analyze if high or low values cluster together or represent spatial anomalies for a chosen variable in a shapefile.

Instructions

Local Moran's I.

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": {
      "shapefile_path": "<shapefile_path>"
    },
    "name": "moran_local"
  }
}

Input Schema

Name	Required	Default
`shapefile_path`	Yes
`dependent_var`	No	LAND_USE
`target_crs`	No	EPSG:4326
`distance_threshold`	No

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 / dependent_var / title
```
Removed value: -"Dependent Var"
```
- removedInput schema / properties / distance_threshold / title
```
Removed value: -"Distance Threshold"
```
- removedInput schema / properties / shapefile_path / title
```
Removed value: -"Shapefile Path"
```
- removedInput schema / properties / target_crs / title
```
Removed value: -"Target Crs"
```
- removedInput schema / title
```
Removed value: -"moran_localArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

D1.8/5.0

Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the method name, with no mention of side effects, data requirements, output characteristics, or any operational constraints. This is completely insufficient for transparency.

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

Conciseness2/5

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

The description is extremely short (three words) but fails to convey necessary information. While it is front-loaded, conciseness is achieved at the expense of utility, making it under-specified rather than efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description does not explain what the tool computes or returns. For a spatial autocorrelation tool with 4 parameters and siblings, the description is far from complete and leaves critical gaps.

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

Parameters1/5

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

Schema coverage is 0%, and the description adds no explanation of parameters (e.g., 'shapefile_path', 'dependent_var', 'distance_threshold'). Defaults are present but their meaning is not described, so the agent cannot infer correct usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Local Moran's I.' identifies the statistical method but lacks a verb or explicit action (e.g., 'computes', 'identifies clusters'). It distinguishes from 'morans_i' (global version) by including 'local', but the purpose remains vague without specifying what the tool actually does.

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 versus siblings like 'getis_ord_g_local' or 'gearys_c'. The description does not mention context, prerequisites, or alternatives, leaving the agent without decision support.

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

Deploy Server