Skip to main content
Glama

get_crs_info

Retrieve coordinate reference system details to understand spatial data projections and transformations for accurate geospatial analysis.

Instructions

Get information about a CRS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'get_crs_info' tool. It takes a CRS identifier as input and returns detailed information about the CRS using the pyproj library, including name, type, axis info, geographic/projected status, datum, ellipsoid, prime meridian, and area of use.
    @gis_mcp.tool()
    def get_crs_info(crs: str) -> Dict[str, Any]:
        """Get information about a CRS."""
        try:
            import pyproj
            crs_obj = pyproj.CRS(crs)
            return {
                "status": "success",
                "name": crs_obj.name,
                "type": crs_obj.type_name,
                "axis_info": [axis.direction for axis in crs_obj.axis_info],
                "is_geographic": crs_obj.is_geographic,
                "is_projected": crs_obj.is_projected,
                "datum": str(crs_obj.datum),
                "ellipsoid": str(crs_obj.ellipsoid),
                "prime_meridian": str(crs_obj.prime_meridian),
                "area_of_use": str(crs_obj.area_of_use) if crs_obj.area_of_use else None,
                "message": "CRS information retrieved successfully"
            }
        except Exception as e:
            logger.error(f"Error getting CRS info: {str(e)}")
            raise ValueError(f"Failed to get CRS info: {str(e)}")
  • MCP resource endpoint that lists the available CRS-related tool operations under 'gis://crs/info', explicitly including 'get_crs_info'.
    @gis_mcp.resource("gis://crs/info")
    def get_crs_info_operations() -> Dict[str, List[str]]:
        """List available CRS information operations."""
        return {
            "operations": [
                "get_crs_info",
                "get_available_crs",
                "get_utm_zone",
                "get_utm_crs",
                "get_geocentric_crs"
            ]
        }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action ('Get information') without disclosing behavioral traits such as whether it's a read-only operation, what format the information is returned in, error handling, or performance considerations. This is inadequate for a tool with no annotation coverage.

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 a single, efficient sentence with no wasted words. It's appropriately sized for a simple tool and front-loaded with the core purpose, though this conciseness comes at the cost of detail.

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

Completeness3/5

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

Given the tool's low complexity (one parameter) and the presence of an output schema (which likely defines return values), the description is minimally adequate. However, with no annotations and 0% schema coverage, it lacks crucial context like parameter semantics and behavioral transparency, making it incomplete for reliable use.

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?

Schema description coverage is 0%, and the description adds no meaning beyond the input schema. It doesn't explain what 'crs' parameter represents (e.g., a CRS code like 'EPSG:4326'), its format, or examples. With one required parameter, the description fails to compensate for the lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose ('Get information about a CRS') with a clear verb ('Get') and resource ('CRS'), but it's vague about what specific information is retrieved. It doesn't differentiate from sibling tools like 'get_available_crs', 'get_geocentric_crs', or 'get_utm_crs', which all involve CRS operations.

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. With siblings like 'get_available_crs' (likely lists CRS options) and 'get_geocentric_crs' (specific CRS type), the description offers no context for selection, leaving usage unclear.

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