GIS MCP Server

by mahdin75

Overview Schema Source Related Servers Discussions Admin

Python

Local

symmetric_difference

Compute the symmetric difference between two geometries, returning the areas that belong exclusively to each geometry.

Instructions

Find symmetric difference between geometries.

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": {
      "geometry1": "<geometry1>",
      "geometry2": "<geometry2>"
    },
    "name": "symmetric_difference"
  }
}

Input Schema

Name	Required	Description	Default
`geometry1`	Yes
`geometry2`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.0Jan 2, 2026

removedInput schema / properties / geometry1 / title
```
Removed value: -"Geometry1"
```
removedInput schema / properties / geometry2 / title
```
Removed value: -"Geometry2"
```

removedInput schema / title

Removed value: -"symmetric_differenceArguments"

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?

With no annotations, the description carries the full burden of behavioral disclosure. It does not state that the tool returns a geometry, nor does it mention any side effects or assumptions about input formats. The simplicity of the operation somewhat mitigates this, but the lack of detail is notable.

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, which is concise but lacks necessary detail. While brevity is valued, here it sacrifices clarity and completeness. The structure is efficient but not effective for guiding an agent.

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?

Given the complexity of geometry operations and the presence of many sibling tools, the description is insufficient. It does not mention the return type (though an output schema exists), nor does it differentiate from similar operations. An agent would need to infer too much from the name alone.

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%, meaning neither parameter has a description. The tool description only says 'geometries' but does not specify accepted formats (e.g., WKT, GeoJSON) or coordinate system expectations. An agent cannot determine how to construct valid inputs without additional context.

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 it finds the symmetric difference between geometries, which is a specific verb and resource. However, it does not distinguish itself from sibling tools like 'difference', 'union', or 'intersection', leaving ambiguity for an agent unfamiliar with geometric operations.

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 is provided on when to use this tool versus alternatives. There is no mention of use cases, when not to use, or comparisons with similar tools like 'difference' or 'union'. This omission increases the risk of incorrect tool selection.

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

Deploy Server