GIS MCP Server

by mahdin75

Overview Schema Source Related Servers Discussions Admin

Python

Local

append_gpd

Read two shapefiles and combine them vertically into one output shapefile for integrated geospatial data.

Instructions

Reads two shapefiles directly, concatenates them vertically.

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": {
      "shapefile1_path": "<shapefile1_path>",
      "shapefile2_path": "<shapefile2_path>",
      "output_path": "<output_path>"
    },
    "name": "append_gpd"
  }
}

Input Schema

Name	Required	Description	Default
`shapefile1_path`	Yes
`shapefile2_path`	Yes
`output_path`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / output_path / title
```
Removed value: -"Output Path"
```
- removedInput schema / properties / shapefile1_path / title
```
Removed value: -"Shapefile1 Path"
```
- removedInput schema / properties / shapefile2_path / title
```
Removed value: -"Shapefile2 Path"
```
- removedInput schema / title
```
Removed value: -"append_gpdArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'reads two shapefiles directly' but does not disclose if inputs are modified, what happens with mismatched schemas, or any side effects.

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

Conciseness3/5

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

The description is a single sentence with no wasted words, but it is too brief. It could be expanded without losing conciseness to add valuable detail.

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

Completeness2/5

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

With 0% schema description coverage and no annotations, the description is insufficient. It does not cover parameter purposes, return behavior, or how the tool handles edge cases like differing geometries.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain any of the three parameters. The tool name and description hint at shapefile paths and output, but no explicit mapping or format details are given.

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?

Description clearly states it concatenates two shapefiles vertically. It uses specific verbs and resources, but does not distinguish from sibling tool merge_gpd, which may perform a similar operation.

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 merge_gpd, dissolve_gpd, or sjoin_gpd. The description implies concatenation but does not describe context or prerequisites.

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

Deploy Server