GIS MCP Server

by mahdin75

Overview Schema Source Related Servers Discussions Admin

Python

Local

scale_geometry

Scale any geometry by independent x and y factors; specify an origin to control the reference point (default: center).

Instructions

Scale 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>",
      "xfact": "<xfact>",
      "yfact": "<yfact>"
    },
    "name": "scale_geometry"
  }
}

Input Schema

Name	Required	Default
`geometry`	Yes
`xfact`	Yes
`yfact`	Yes
`origin`	No	center

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 / origin / title
```
Removed value: -"Origin"
```
- removedInput schema / properties / xfact / title
```
Removed value: -"Xfact"
```
- removedInput schema / properties / yfact / title
```
Removed value: -"Yfact"
```
- removedInput schema / title
```
Removed value: -"scale_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 present, so the description must convey behavioral traits. It only says 'Scale a geometry' without explaining what scaling entails (e.g., origin, coordinate modifications), whether it mutates input or returns a new geometry, or any side effects.

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?

While the description is a single sentence, it is under-specified for a tool with four parameters and many siblings. Conciseness is sacrificed for completeness; the description fails to inform.

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 complexity of scaling geometry and the presence of similar sibling tools, the description is grossly incomplete. It lacks details on coordinate systems, output behavior, and integration with other operations, making it difficult for an agent to use correctly.

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?

The input schema has 0% description coverage, and the tool description adds no information about parameters. The roles of 'xfact', 'yfact', 'origin', and the format of 'geometry' are completely unexplained, leaving the agent without guidance on how to fill them.

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 the action 'scale' and the resource 'geometry'. However, it does not distinguish this tool from similar sibling tools like translate_geometry or rotate_geometry, which also modify 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 is provided on when to use this tool versus alternatives or when not to use it. The description only states the basic purpose, leaving the agent to infer usage context.

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

Deploy Server