GIS MCP Server

by mahdin75

Overview Schema Source Related Servers Discussions Admin

Python

Local

translate_geometry

Shift a geometry to a new location by specifying X, Y, and optional Z offset values.

Instructions

Translate a geometry.

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": {
      "geometry": "<geometry>",
      "xoff": "<xoff>",
      "yoff": "<yoff>"
    },
    "name": "translate_geometry"
  }
}

Input Schema

Name	Required	Description	Default
`geometry`	Yes
`xoff`	Yes
`yoff`	Yes
`zoff`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / geometry / title
```
Removed value: -"Geometry"
```
- removedInput schema / properties / xoff / title
```
Removed value: -"Xoff"
```
- removedInput schema / properties / yoff / title
```
Removed value: -"Yoff"
```
- removedInput schema / properties / zoff / title
```
Removed value: -"Zoff"
```
- removedInput schema / title
```
Removed value: -"translate_geometryArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

C2.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that the operation is non-destructive, what coordinate system is used, or that zoff is optional. The minimal statement adds little beyond the tool name.

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

Conciseness2/5

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

The description is a single short sentence, which is concise but at the cost of missing essential information. It is not adequately structured to help an agent decide or invoke the tool correctly.

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?

The tool has 4 parameters, no annotations, and an output schema (not shown). The description fails to provide context on input format, output, or behavior. It is severely incomplete for a meaningful tool invocation.

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?

Schema description coverage is 0%, so the description must explain parameters. It does not clarify what 'geometry' format (WKT, GeoJSON) is expected, nor the meaning of xoff, yoff, zoff. The description adds no value over the raw schema.

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 'Translate a geometry' clearly states the verb and resource. In geometry contexts, 'translate' means shifting by offsets. This distinguishes it from sibling tools like rotate, scale, snap, and project. However, it could be more explicit about the offsets, so it's not a 5.

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?

The description provides no guidance on when to use this tool versus alternatives like rotate_geometry or scale_geometry. There is no mention of typical use cases or constraints.

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

Deploy Server