GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

join_counts

Computes global binary join counts to measure spatial autocorrelation of a binary variable in shapefile features, with configurable CRS and distance threshold.

Instructions

Global Binary Join Counts.

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

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

TDQS

D1.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It gives no indication of side effects, read-only nature, or authorization needs. 'Counts' implies a read operation, but this is not explicit.

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 a phrase, not a full sentence. While brief, it is under-specified and lacks structure, making it unhelpful for an agent.

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 tool has 4 parameters, an output schema, and complex spatial analysis context, the description is severely incomplete. No explanation of the output or how parameters influence results is provided.

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%, and the description provides no information about parameters such as 'shapefile_path', 'dependent_var', 'target_crs', or 'distance_threshold'. The agent gets no help understanding their roles or defaults.

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

Purpose2/5

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

The description 'Global Binary Join Counts' is vague and lacks a verb. It does not clearly state what the tool does, such as whether it computes or returns join counts. The term 'join counts' is ambiguous without context.

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 guidance is provided. The description does not indicate when to use this tool versus alternatives like 'join_counts_local' or other spatial statistics tools on the server.

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

Deploy Server