Skip to main content
Glama
Sign In
GIS MCP Server

GIS MCP Server

by mahdin75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

project_geometry

Reproject a geometry from one CRS to another. Input geometry as GeoJSON, source CRS, and target CRS.

Instructions

Project a geometry between CRS.

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>",
      "source_crs": "<source_crs>",
      "target_crs": "<target_crs>"
    },
    "name": "project_geometry"
  }
}

Input Schema

NameRequiredDescriptionDefault
geometryYes
source_crsYes
target_crsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.0
    • removedInput schema / properties / geometry / title
      Removed value: -"Geometry"
    • removedInput schema / properties / source_crs / title
      Removed value: -"Source Crs"
    • removedInput schema / properties / target_crs / title
      Removed value: -"Target Crs"
    • removedInput schema / title
      Removed value: -"project_geometryArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only mentions 'project' without explaining traits like CRS format expectations, handling of invalid geometries, or 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?

The description is overly brief; it prioritizes brevity over completeness. While short, it fails to include essential details that would justify its length.

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 three required parameters and an output schema, the description lacks sufficient detail. It does not mention the output type or any constraints, making it incomplete for a tool of moderate complexity.

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

Parameters2/5

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

Input schema has 0% description coverage, and the description adds no extra meaning beyond parameter names. It does not specify formats for geometry (e.g., GeoJSON) or CRS identifiers, which are critical for correct use.

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 tool projects a geometry between CRS, specifying the verb and resource. However, it does not differentiate from sibling tools like reproject_raster or transform_coordinates, which could cause confusion.

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. There is no mention of prerequisites, context, or exclusions, leaving the agent without direction.

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

Deploy Server

Other Tools