GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

rotate_geometry

Rotate a geometry around an origin point by a specified angle. Choose between degrees and radians, and set the origin to center or a custom point for precise spatial transformations.

Instructions

Rotate 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>",
      "angle": "<angle>"
    },
    "name": "rotate_geometry"
  }
}

Input Schema

Name	Required	Default
`geometry`	Yes
`angle`	Yes
`origin`	No	center
`use_radians`	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 / angle / title
```
Removed value: -"Angle"
```
- removedInput schema / properties / geometry / title
```
Removed value: -"Geometry"
```
- removedInput schema / properties / origin / title
```
Removed value: -"Origin"
```
- removedInput schema / properties / use_radians / title
```
Removed value: -"Use Radians"
```
- removedInput schema / title
```
Removed value: -"rotate_geometryArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

C2.4/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 but only states 'Rotate a geometry.' No mention of side effects, permissions, or behavior beyond the basic action.

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 concise (single sentence), but it lacks necessary substance to be helpful.

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 rotation (geometry format, rotation point, angle units), the description is too minimal and incomplete. Output schema exists but is not leveraged.

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%, and the description adds no meaning to parameters like geometry format, angle unit, or origin options. The description provides no value beyond parameter names.

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 states the verb 'rotate' and the resource 'geometry', clearly indicating the tool's purpose. However, it does not differentiate from sibling tools like 'scale_geometry' or 'translate_geometry'.

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 versus alternatives, no prerequisites or context provided.

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

Deploy Server