Skip to main content
Glama

join_counts_local

Calculate local spatial autocorrelation by analyzing attribute similarity between neighboring geographic features within a specified distance threshold.

Instructions

Local Join Counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shapefile_pathYes
dependent_varNoLAND_USE
target_crsNoEPSG:4326
distance_thresholdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function for the 'join_counts_local' tool. Loads spatial data, creates distance-based weights, handles isolated units, computes local join counts using esda.Join_Counts_Local, and returns results with preview.
    @gis_mcp.tool()
    def join_counts_local(shapefile_path: str, dependent_var: str = "LAND_USE", target_crs: str = "EPSG:4326",
                          distance_threshold: float = 100000) -> Dict[str, Any]:
        """Local Join Counts."""
        gdf, y, w, (threshold, unit), err = pysal_load_data(shapefile_path, dependent_var, target_crs, distance_threshold)
        if err:
            return {"status": "error", "message": err}
    
        # Handle islands - if all points are islands, fall back to KNN weights for connectivity
        import libpysal
        if w.islands:
            if len(w.islands) == len(gdf):
                # All points are islands - fall back to KNN weights
                try:
                    # Use k=4 for a 5x5 grid to ensure connectivity
                    w = libpysal.weights.KNN.from_dataframe(gdf, k=4)
                    w.transform = 'r'
                except Exception as e:
                    return {"status": "error", "message": f"All units are islands and KNN fallback failed: {str(e)}"}
            else:
                # Some islands - filter them out
                keep_idx = [i for i in range(len(gdf)) if i not in set(w.islands)]
                if len(keep_idx) == 0:
                    return {"status": "error", "message": "All units are islands (no neighbors). Try increasing distance_threshold."}
                # Filter data
                gdf_filtered = gdf.iloc[keep_idx].reset_index(drop=True)
                y_filtered = y[keep_idx]
                # Rebuild weights without islands using the same threshold
                w_filtered = libpysal.weights.DistanceBand.from_dataframe(
                    gdf_filtered, 
                    threshold=threshold,  # Use the effective threshold already calculated in pysal_load_data
                    binary=False
                )
                w_filtered.transform = 'r'
                gdf, y, w = gdf_filtered, y_filtered, w_filtered
    
        import esda
        stat = esda.Join_Counts_Local(y, w)
        preview = gdf[['geometry', dependent_var]].head(5).copy()
        preview['geometry'] = preview['geometry'].apply(lambda g: g.wkt)
    
        # Join_Counts_Local has LJC attribute
        ljc_val = None
        if hasattr(stat, "LJC"):
            ljc_val = stat.LJC.tolist() if hasattr(stat.LJC, "tolist") else list(stat.LJC)
        elif hasattr(stat, "local_join_counts"):
            ljc_val = stat.local_join_counts.tolist() if hasattr(stat.local_join_counts, "tolist") else list(stat.local_join_counts)
        elif hasattr(stat, "ljc"):
            ljc_val = stat.ljc.tolist() if hasattr(stat.ljc, "tolist") else list(stat.ljc)
        
        return {
            "status": "success",
            "message": f"Local Join Counts completed successfully (threshold: {threshold} {unit})",
            "result": {
                "local_join_counts": ljc_val,
                "data_preview": preview.to_dict(orient="records")
            }
        }
  • Helper function used by join_counts_local (and other tools) to load GeoDataFrame from shapefile, reproject, extract dependent variable, create and row-standardize distance band spatial weights, and handle basic island isolation.
    def pysal_load_data(shapefile_path: str, dependent_var: str, target_crs: str, distance_threshold: float):
        """Common loader and weight creation for esda statistics."""
        if not os.path.exists(shapefile_path):
            return None, None, None, None, f"Shapefile not found: {shapefile_path}"
    
        gdf = gpd.read_file(shapefile_path)
        if dependent_var not in gdf.columns:
            return None, None, None, None, f"Dependent variable '{dependent_var}' not found in shapefile columns"
    
        gdf = gdf.to_crs(target_crs)
    
        effective_threshold = distance_threshold
        unit = "meters"
        if target_crs.upper() == "EPSG:4326":
            effective_threshold = distance_threshold / 111000
            unit = "degrees"
    
        y = gdf[dependent_var].values.astype(np.float64)
        import libpysal
        w = libpysal.weights.DistanceBand.from_dataframe(gdf, threshold=effective_threshold, binary=False)
        w.transform = 'r'
    
        for island in w.islands:
            w.weights[island] = [0] * len(w.weights[island])
            w.cardinalities[island] = 0
    
        return gdf, y, w, (effective_threshold, unit), None
  • GIS resource endpoint listing available ESDA/PySAL operations, including 'join_counts_local' as one of the supported tools.
    @gis_mcp.resource("gis://operations/esda")
    def get_spatial_operations() -> Dict[str, List[str]]:
        """List available spatial analysis operations. This is for esda library. They are using pysal library."""
        return {
            "operations": [
                "getis_ord_g",
                "morans_i",
                "gearys_c",
                "gamma_statistic",
                "moran_local",
                "getis_ord_g_local",
                "join_counts",
                "join_counts_local",
                "adbscan"
            ]
        }
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to do so, offering no information on what the tool does (e.g., whether it performs calculations, modifies data, or outputs results), its side effects, or any constraints like performance or data handling.

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 overly concise to the point of under-specification, consisting of only three words that fail to convey meaningful information. While not verbose, it lacks the necessary structure or content to be useful, making it inefficient rather than appropriately concise.

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?

Given the complexity implied by four parameters and the presence of an output schema, the description is completely inadequate. It does not explain the tool's function, inputs, or outputs, failing to provide any context needed for an agent to understand or invoke the tool correctly, despite the output schema potentially covering return values.

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%, meaning parameters are undocumented in the schema. The description does not compensate by explaining any parameters, their purposes, or how they relate to the tool's function, leaving all four parameters (e.g., 'shapefile_path', 'dependent_var') without semantic context.

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

Purpose1/5

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

The description 'Local Join Counts.' is a tautology that merely restates the tool name without specifying what it does. It lacks a clear verb (e.g., 'calculate', 'compute') and does not identify the resource or operation, making it impossible to distinguish from sibling tools like 'join_counts' or understand its purpose.

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

Usage Guidelines1/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 alternatives. It does not mention any context, prerequisites, or exclusions, and with sibling tools like 'join_counts' present, there is no indication of how this tool differs or when it should be selected.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mahdin75/gis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server