GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

sjoin_nearest_gpd

Perform a nearest neighbor spatial join between two geospatial files, matching features by minimum distance. Choose left or right join, set an optional maximum distance, and save the result to a specified path.

Instructions

Nearest neighbor spatial join using geopandas.sjoin_nearest. Args: left_path: Path to the left geospatial file. right_path: Path to the right geospatial file. how: Type of join ('left', 'right'). max_distance: Optional maximum search distance. output_path: Optional path to save the result. Returns: Dictionary with status, message, and output info.

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": {
      "left_path": "<left_path>",
      "right_path": "<right_path>"
    },
    "name": "sjoin_nearest_gpd"
  }
}

Input Schema

Name	Required	Default
`left_path`	Yes
`right_path`	Yes
`how`	No	left
`max_distance`	No
`output_path`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / how / title
```
Removed value: -"How"
```
- removedInput schema / properties / left_path / title
```
Removed value: -"Left Path"
```
- addedInput schema / properties / max_distance / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / max_distance / title
```
Removed value: -"Max Distance"
```
- removedInput schema / properties / max_distance / type
```
Removed value: -"number"
```
- addedInput schema / properties / output_path / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / output_path / title
```
Removed value: -"Output Path"
```
- removedInput schema / properties / output_path / type
```
Removed value: -"string"
```
- removedInput schema / properties / right_path / title
```
Removed value: -"Right Path"
```
- removedInput schema / title
```
Removed value: -"sjoin_nearest_gpdArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description is the sole source of behavioral info. It only states the operation and parameters, but omits side effects (e.g., file creation, data mutation), permissions, performance implications, or error handling. The return type is vaguely described as 'Dictionary with status, message, and output info' without specifics.

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

Conciseness4/5

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

The description is concise with a clear structure (Args and Returns sections) and no superfluous content. However, the Returns section is vague and could be slightly more informative without losing conciseness.

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

Completeness3/5

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

Given 5 parameters, no annotations, and an output schema (though not detailed in context), the description covers basic functionality but lacks guidance on output structure, edge cases, or integration with sibling tools. It is adequate for a straightforward tool but leaves several behavioral aspects unaddressed.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It provides basic meanings for each parameter (e.g., 'Path to the left geospatial file'), going beyond just type definitions. However, it lacks details on formats, unit for max_distance, and default behaviors, making it minimally helpful but not thorough.

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 'Nearest neighbor spatial join using geopandas.sjoin_nearest', explicitly specifying the verb ('join') and the resource (geospatial data). It distinguishes itself from siblings like sjoin_gpd by emphasizing 'nearest neighbor', making the tool's unique purpose unambiguous.

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

Usage Guidelines3/5

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

The description implies usage for nearest neighbor joins, but does not explicitly state when to use this tool over alternatives like sjoin_gpd (exact spatial join) or other operations. No when-to-use or when-not-to-use guidance is provided, leaving the agent to infer from the tool name and description.

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

Deploy Server