Skip to main content
Glama

geometry_to_geojson

Convert WKT geometry strings to GeoJSON format for geospatial analysis in GIS applications.

Instructions

Convert a Shapely geometry (WKT) to GeoJSON using shapely.geometry.mapping. Args: geometry: WKT string of the geometry. Returns: Dictionary with status, message, and GeoJSON representation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geometryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'geometry_to_geojson' tool. Converts a WKT geometry string to GeoJSON using Shapely's mapping function.
    @gis_mcp.tool()
    def geometry_to_geojson(geometry: str) -> Dict[str, Any]:
        """
        Convert a Shapely geometry (WKT) to GeoJSON using shapely.geometry.mapping.
        Args:
            geometry: WKT string of the geometry.
        Returns:
            Dictionary with status, message, and GeoJSON representation.
        """
        try:
            from shapely import wkt
            from shapely.geometry import mapping
            geom = wkt.loads(geometry)
            geojson = mapping(geom)
            return {
                "status": "success",
                "geojson": geojson,
                "message": "Geometry converted to GeoJSON successfully"
            }
        except Exception as e:
            logger.error(f"Error in geometry_to_geojson: {str(e)}")
            return {"status": "error", "message": str(e)}
  • Resource handler that lists 'geometry_to_geojson' as an available Shapely utility operation.
    @gis_mcp.resource("gis://operations/shapely_util")
    def get_shapely_util_operations() -> Dict[str, List[str]]:
        """List available Shapely utility/advanced operations."""
        return {
            "operations": [
                "snap_geometry",
                "nearest_point_on_geometry",
                "normalize_geometry",
                "geometry_to_geojson",
                "geojson_to_geometry"
            ]
        }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It mentions the conversion method ('using shapely.geometry.mapping') and return structure ('Dictionary with status, message, and GeoJSON representation'), which adds useful behavioral context beyond basic input-output. However, it doesn't cover error conditions, performance characteristics, or validation requirements.

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

Conciseness5/5

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

The description is efficiently structured with a clear purpose statement followed by separate 'Args' and 'Returns' sections. Every sentence earns its place, and the information is front-loaded with the core functionality stated first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (single parameter conversion), no annotations, but with an output schema present, the description provides adequate context. It explains the conversion purpose, parameter semantics, and return structure, though it could benefit from more detail about error handling or example usage.

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?

The schema has 0% description coverage, but the description compensates by explaining the single parameter 'geometry' as 'WKT string of the geometry', providing crucial semantic information about the expected format. This goes beyond what the bare schema provides, though it doesn't detail WKT syntax or validation rules.

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 clearly states the tool's purpose with specific verb ('Convert'), resource ('Shapely geometry (WKT)'), and target format ('GeoJSON'), and distinguishes it from its sibling 'geojson_to_geometry' by specifying the opposite conversion direction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through the mention of 'Shapely geometry (WKT)' and 'shapely.geometry.mapping', suggesting it's for users working with Python's Shapely library. However, it doesn't explicitly state when to use this tool versus alternatives or provide any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mahdin75/gis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server