GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

clip_vector

Clip vector geometries to a specified boundary using geopandas. Supply an input geospatial file and a clipping geometry to extract features within the clip area.

Instructions

Clip vector geometries using geopandas.clip. Args: gdf_path: Path to the input geospatial file. clip_path: Path to the clipping geometry file. 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": {
      "gdf_path": "<gdf_path>",
      "clip_path": "<clip_path>"
    },
    "name": "clip_vector"
  }
}

Input Schema

Name	Required	Description	Default
`gdf_path`	Yes
`clip_path`	Yes
`output_path`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / clip_path / title
```
Removed value: -"Clip Path"
```
- removedInput schema / properties / gdf_path / title
```
Removed value: -"Gdf Path"
```
- 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: -"clip_vectorArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions using 'geopandas.clip' and returns a dict, but fails to specify side effects (e.g., file creation/overwriting), error handling for missing files or CRS mismatches, or whether it is a read-only operation.

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?

Description is short and structured with 'Args:' and 'Returns:' sections. The core purpose is stated in one sentence. No unnecessary words, though it could be more informative without being verbose.

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?

Despite a simple operation, the description lacks details on when to prefer this over similar tools (e.g., 'intersection', 'difference'). The output schema is not shown, and return description is basic. In a tool-rich environment, more context is needed.

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 coverage is 0%, so description must compensate. It adds minimal context beyond parameter names: 'Path to the input geospatial file' for gdf_path is vague. No details on supported formats, paths relative rules, or behavior of output_path when null.

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?

Clearly states the action ('clip') and resource ('vector geometries') using a specific verb+resource. It distinguishes itself from sibling geometry tools like 'buffer' or 'intersection' through the unique operation name, but lacks explicit differentiation statements.

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 over alternatives like 'difference' or 'intersection'. Does not mention prerequisites such as CRS compatibility or file requirements, leaving the agent with little context for decision-making.

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

Deploy Server