GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

intersection

Given two geometries, compute their intersection to obtain the overlapping region. Provide geometry1 and geometry2 as input strings.

Instructions

Find intersection of two 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": "intersection"
  }
}

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: -"intersectionArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

C2.5/5.0

Behavior1/5

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

The description lacks any behavioral disclosure beyond the basic operation. No annotations are provided, so the description carries full burden but fails to mention input format requirements, output details, error behavior, or performance characteristics.

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 extremely concise at five words, but it successfully conveys the tool's core purpose. However, it sacrifices necessary detail for brevity, which is acceptable but not optimal given the tool's complexity and lack of annotation support.

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

Completeness1/5

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

Given the presence of an output schema and numerous sibling tools, the description is severely incomplete. It fails to explain what the intersection represents conceptually, how inputs should be formatted, or what the output structure is, leaving the agent without critical usage context.

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

Parameters1/5

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

With 0% schema description coverage, the description adds no meaning to the parameters beyond their names ('geometry1', 'geometry2'). It does not specify accepted geometry formats (e.g., WKT, GeoJSON) or clarify whether the parameters represent points, lines, or polygons.

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 'Find intersection of two geometries,' which is a specific verb+resource combination. It effectively distinguishes this tool from sibling tools like union, difference, and symmetric_difference, which handle related but distinct 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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives like clip_vector or point_in_polygon, nor does it mention prerequisites or context-specific scenarios.

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

Deploy Server