Skip to main content
Glama

get_geod_info

Retrieve geodetic calculation parameters like ellipsoid dimensions and flattening for accurate coordinate transformations in GIS analysis.

Instructions

Get information about a geodetic calculation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ellpsNoWGS84
aNo
bNo
fNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_geod_info' tool, decorated with @gis_mcp.tool(). It creates a pyproj.Geod object and returns ellipsoid parameters (a, b, f, es, e).
    @gis_mcp.tool()
    def get_geod_info(ellps: str = "WGS84", a: Optional[float] = None,
                    b: Optional[float] = None, f: Optional[float] = None) -> Dict[str, Any]:
        """Get information about a geodetic calculation."""
        try:
            import pyproj
            geod = pyproj.Geod(ellps=ellps, a=a, b=b, f=f)
            # Calculate e (eccentricity) from es (first eccentricity squared)
            e = (geod.es ** 0.5) if geod.es >= 0 else None
            
            return {
                "status": "success",
                "ellps": ellps,  # Return the parameter, not attribute
                "ellipsoid": ellps,  # Also include as ellipsoid for compatibility
                "a": geod.a,
                "b": geod.b,
                "f": geod.f,
                "es": geod.es,
                "e": e,
                "message": "Geodetic information retrieved successfully"
            }
        except Exception as e:
            logger.error(f"Error getting geodetic info: {str(e)}")
            raise ValueError(f"Failed to get geodetic info: {str(e)}")
  • Import of pyproj_functions.py in the main entry point, which executes the @gis_mcp.tool() decorators to register the 'get_geod_info' tool with the FastMCP instance.
    from . import (
        geopandas_functions,
        shapely_functions,
        rasterio_functions,
        pyproj_functions,
        pysal_functions,
    )
  • GIS resource that lists 'get_geod_info' as one of the available geodetic operations for discovery.
    @gis_mcp.resource("gis://crs/geodetic")
    def get_geodetic_operations() -> Dict[str, List[str]]:
        """List available geodetic operations."""
        return {
            "operations": [
                "get_geod_info",
                "calculate_geodetic_distance",
                "calculate_geodetic_point",
                "calculate_geodetic_area"
            ]
        }
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 of behavioral disclosure. It mentions 'Get information' but does not specify if this is a read-only operation, what permissions might be needed, or any rate limits. The description is minimal and fails to add meaningful context beyond the basic action, leaving behavioral traits unclear.

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 is front-loaded and appropriately sized for the tool's apparent simplicity, though this conciseness may contribute to under-specification in other dimensions.

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 moderate complexity (4 parameters, no annotations, but with an output schema), the description is incomplete. It does not explain what information is returned, how parameters affect the output, or tie into sibling tools. The output schema may cover return values, but the description lacks context on usage and behavior, making it minimally adequate but with clear gaps.

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%, so the description must compensate for undocumented parameters. It adds no information about the four parameters (ellps, a, b, f), such as their roles in geodetic calculations, default behaviors, or interdependencies. This leaves parameters largely unexplained, with only the schema providing basic types and defaults.

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 'Get information about a geodetic calculation,' which provides a vague purpose without specifying what information is retrieved or what 'geodetic calculation' entails. It distinguishes from siblings like 'calculate_geodetic_area' or 'calculate_geodetic_distance' by focusing on information retrieval rather than computation, but lacks specificity about the resource or output.

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. Siblings include tools like 'get_available_crs' or 'get_crs_info' for coordinate system information, but the description does not clarify if this tool is for ellipsoid parameters, geodetic formulas, or other metadata, leaving usage context implied at best.

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