GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

build_and_transform_weights

Construct and transform spatial weight matrices from point datasets. Supports contiguity (queen, rook), distance-based, and KNN methods with row, variance, binary, or other transformations.

Instructions

Build and transform spatial weights in one step.

Parameters:

data_path: Path to point shapefile or GeoPackage
method: 'queen', 'rook', 'distance_band', or 'knn'
id_field: Optional field name for IDs
threshold: Distance threshold (required if method='distance_band')
k: Number of neighbors (required if method='knn')
binary: True for binary weights, False for inverse distance (DistanceBand only)
transform_type: 'r', 'v', 'b', 'o', or 'd'

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": {
      "data_path": "<data_path>"
    },
    "name": "build_and_transform_weights"
  }
}

Input Schema

Name	Required	Default
`data_path`	Yes
`method`	No	queen
`id_field`	No
`threshold`	No
`k`	No
`binary`	No
`transform_type`	No	r

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / binary / title
```
Removed value: -"Binary"
```
- removedInput schema / properties / data_path / title
```
Removed value: -"Data Path"
```
- removedInput schema / properties / id_field / title
```
Removed value: -"Id Field"
```
- removedInput schema / properties / k / title
```
Removed value: -"K"
```
- removedInput schema / properties / method / title
```
Removed value: -"Method"
```
- removedInput schema / properties / threshold / title
```
Removed value: -"Threshold"
```
- removedInput schema / properties / transform_type / title
```
Removed value: -"Transform Type"
```
- removedInput schema / title
```
Removed value: -"build_and_transform_weightsArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, so description must cover behavioral aspects. It describes building and transforming weights and parameter details but does not disclose what the output is (e.g., returns a pysal weights object), side effects, or permissions. The output schema exists but is not referenced in the description.

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 well-organized with a clear list of parameters and explanations. It is informative but slightly lengthy; could be tightened by removing redundant default value notes. Still, it front-loads the core action and uses bullet points effectively.

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 7 parameters, no schema descriptions, and no annotations, the description covers parameter semantics well but omits the tool's return behavior (despite existence of output schema) and any prerequisites (e.g., valid file path). This gap reduces completeness for an agent deciding to invoke the tool.

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

Parameters4/5

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

Input schema has 0% description coverage, so the description adds crucial meaning by explaining each parameter, including conditional requirements (e.g., threshold for distance_band). It specifies allowed methods and transform types. However, it lacks examples or more detailed constraints for enum-like parameters.

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 explicitly states it builds and transforms spatial weights in one step, with clear verb ('build_and_transform'), resource ('weights'), and lists parameters. It distinguishes from siblings like 'weights_from_shapefile' (only build) and 'build_transform_and_save_weights' (build and transform then save).

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 explicit guidance on when to use this tool versus alternatives. It mentions 'in one step' but does not compare with separate build and transform tools or other siblings like 'distance_band_weights' or 'knn_weights'. No when-not-to-use or prerequisite conditions are given.

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

Deploy Server