GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

overlay_gpd

Perform spatial overlay analysis on two geospatial files using intersection, union, identity, symmetric difference, or difference methods. Returns overlay results as a new GeoDataFrame.

Instructions

Overlay two GeoDataFrames using geopandas.overlay. Args: gdf1_path: Path to the first geospatial file. gdf2_path: Path to the second geospatial file. how: Overlay method ('intersection', 'union', 'identity', 'symmetric_difference', 'difference'). 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": {
      "gdf1_path": "<gdf1_path>",
      "gdf2_path": "<gdf2_path>"
    },
    "name": "overlay_gpd"
  }
}

Input Schema

Name	Required	Default
`gdf1_path`	Yes
`gdf2_path`	Yes
`how`	No	intersection
`output_path`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / gdf1_path / title
```
Removed value: -"Gdf1 Path"
```
- removedInput schema / properties / gdf2_path / title
```
Removed value: -"Gdf2 Path"
```
- removedInput schema / properties / how / title
```
Removed value: -"How"
```
- 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 / title
```
Removed value: -"overlay_gpdArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It states it uses geopandas.overlay and returns a dict with status, message, and output info, but lacks details on error handling, side effects, or prerequisites (e.g., file existence, CRS matching).

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 and well-structured with a docstring format (Args, Returns). It front-loads the main purpose and provides necessary details without extraneous text.

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 the tool's complexity (4 params, output schema exists), the description covers param descriptions and return structure. However, it could be more complete by mentioning file format expectations and CRS handling, and referencing siblings.

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 coverage is 0%, so description must add meaning. It explains each parameter's purpose and lists valid options for 'how', but does not specify expected file formats or path requirements.

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

Purpose4/5

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

The description clearly states the verb 'overlay' and resource 'GeoDataFrames', and mentions using geopandas.overlay. It distinguishes from siblings by being a generic overlay tool with a 'how' parameter, but could be more explicit about its flexibility.

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 guidance on when to use this tool versus alternatives like the specific intersection, union, etc. siblings. The description only explains what it does, not when it's appropriate.

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

Deploy Server