GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

gamma_statistic

Compute the Gamma statistic to measure spatial autocorrelation in geographic data. Define shapefile path, dependent variable, target CRS, and distance threshold to analyze clustering patterns.

Instructions

Compute Gamma Statistic for spatial autocorrelation.

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": "gamma_statistic"
  }
}

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: -"gamma_statisticArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

C2.2/5.0

Behavior2/5

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

With no annotations and a minimal description, the behavioral transparency is poor. The description does not disclose side effects, computational requirements, or constraints like data size or coordinate system handling.

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 concise at one sentence, but it sacrifices critical information. While every word is earned, the brevity leads to omission of necessary context.

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

Completeness2/5

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

Given the tool's complexity and many siblings, the description is incomplete. An output schema exists but doesn't compensate for the lack of explanation about what the Gamma Statistic measures and how it differs from other autocorrelation tests.

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 description coverage is 0%, but the description adds no information about parameters. Keys like 'distance_threshold' and 'dependent_var' remain unexplained, forcing the agent to rely on names alone.

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 clearly states the verb 'Compute' and resource 'Gamma Statistic' with context 'spatial autocorrelation', providing a basic purpose. However, it does not differentiate from sibling tools like morans_i or gearys_c, leaving ambiguity about when to use this specific statistic.

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 usage guidelines are provided. The description lacks any indication of when to use this tool versus alternatives, what prerequisites are needed (e.g., data type, variable assumptions), or typical use cases.

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

Deploy Server