arcgis-mcp-bridge

Overview Schema Source Related Servers Discussions Admin

hotspot_analysis

Identify statistically significant clusters of high and low values in geographic data using Getis-Ord Gi* analysis. Use it to find hot and cold spots in incidents, indicators, or measurements.

Instructions

Run Getis-Ord Gi* hot and cold spot analysis using ArcPy HotSpots and write a feature class with GiZScore, GiPValue, and Gi_Bin results. Use this to identify statistically significant clusters of high and low values in incidents, socioeconomic indicators, service demand, or environmental measurements. Supports spatial conceptualization, distance method, and optional distance band.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.6.3Jul 4, 2026

addedInput schema / $defs / HotspotAnalysisInput / description

Added value: +"Input contract for identifying statistically significant hot and cold spots."

addedInput schema / $defs / HotspotAnalysisInput / properties / conceptualization / description

Added value: +"Spatial relationship model used to define feature neighbors, such as FIXED_DISTANCE_BAND, INVERSE_DISTANCE, K_NEAREST_NEIGHBORS, or contiguity-based relationships."

changedInput schema / $defs / HotspotAnalysisInput / properties / distance_band / description

Previous value: -"Band/threshold in map units."New value: +"Optional distance threshold in map units used by distance-based conceptualizations. Use None when ArcPy should infer or not require a distance band."

addedInput schema / $defs / HotspotAnalysisInput / properties / distance_method / description

Added value: +"Distance calculation method used for spatial relationships. Use EUCLIDEAN_DISTANCE for straight-line distance or MANHATTAN_DISTANCE for grid-like movement."

addedInput schema / $defs / HotspotAnalysisInput / properties / in_features / description

Added value: +"Absolute path to the input feature class used for spatial statistics. The path must be inside a configured PathGuard allowed root."

changedInput schema / $defs / HotspotAnalysisInput / properties / input_field / description

Previous value: -"Numeric field analyzed for clustering."New value: +"Numeric attribute field analyzed for statistically significant spatial clustering of high and low values."

addedInput schema / $defs / HotspotAnalysisInput / properties / out_features / description

Added value: +"Absolute output feature class path to create with statistical results. The path must be inside a configured PathGuard allowed root; existing outputs require overwrite=true."

addedInput schema / $defs / HotspotAnalysisInput / properties / overwrite / description

Added value: +"Set true only when replacing an existing spatial statistics output feature class is intended."

First observedv1.0.0Jul 4, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so the description carries the full burden. It discloses that the tool creates a feature class (write operation) and lists output fields, but does not mention prerequisites like ArcGIS license, performance implications, or error handling.

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?

Two concise sentences: the first states the core action and output, the second provides usage guidance and parameter summary. No wasted words.

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 tool's complexity (spatial statistics) and the presence of parameter descriptions in the schema, the description covers the algorithm, output fields, use case, and supported parameters. It is mostly complete, though it could mention that the input field must be numeric.

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 context indicates 0% schema description coverage, so the description must compensate. It adds context about the algorithm (ArcPy HotSpots) and result fields, and summarizes the key parameters (spatial conceptualization, distance method, optional distance band). However, it does not detail parameter constraints beyond what the schema already provides.

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 runs Getis-Ord Gi* hot and cold spot analysis using ArcPy HotSpots and writes a feature class with specific result fields (GiZScore, GiPValue, Gi_Bin). The purpose is specific and distinct from sibling tools like spatial_autocorrelation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states when to use the tool ('identify statistically significant clusters') and mentions supported parameters, but does not explicitly say when not to use it or identify alternatives among sibling tools.

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

Deploy Server