Skip to main content
Glama

calculate_geodetic_point

Calculate a new geographic point from a starting location using distance and direction for geospatial analysis and mapping applications.

Instructions

Calculate point at given distance and azimuth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_pointYes
azimuthYes
distanceYes
ellpsNoWGS84

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'calculate_geodetic_point' MCP tool. It is decorated with @gis_mcp.tool(), which registers it as an MCP tool. The function computes a new geodetic point using pyproj.Geod.fwd given a starting point, azimuth, distance, and ellipsoid parameters.
    @gis_mcp.tool()
    def calculate_geodetic_point(start_point: List[float], azimuth: float, 
                            distance: float, ellps: str = "WGS84") -> Dict[str, Any]:
        """Calculate point at given distance and azimuth."""
        try:
            import pyproj
            geod = pyproj.Geod(ellps=ellps)
            lon, lat = start_point
            lon2, lat2, back_azimuth = geod.fwd(lon, lat, azimuth, distance)
            return {
                "status": "success",
                "point": [lon2, lat2],
                "back_azimuth": back_azimuth,
                "ellps": ellps,
                "message": "Geodetic point calculated successfully"
            }
        except Exception as e:
            logger.error(f"Error calculating geodetic point: {str(e)}")
            raise ValueError(f"Failed to calculate geodetic point: {str(e)}")
  • Resource listing that advertises the availability of the 'calculate_geodetic_point' tool under the 'gis://crs/geodetic' namespace, aiding in tool discovery.
    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 states the tool calculates a point but doesn't explain what the output is (e.g., coordinates), any assumptions (e.g., units for distance/azimuth), error handling, or performance considerations. This is inadequate for a tool with parameters and an output schema.

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, direct sentence with no wasted words. It's front-loaded and efficiently conveys the core action, making it highly concise and well-structured for quick understanding.

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 complexity (geodetic calculation with 4 parameters), lack of annotations, and 0% schema coverage, the description is incomplete. However, the presence of an output schema reduces the need to explain return values. The description provides a basic purpose but misses key details like parameter definitions and behavioral context, making it minimally adequate.

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%, meaning parameters are undocumented in the schema. The description mentions 'distance and azimuth' but doesn't define them or cover 'start_point' and 'ellps'. It adds minimal meaning beyond the schema, failing to compensate for the lack of schema documentation, especially with 4 parameters.

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 'Calculate point at given distance and azimuth' clearly states the action (calculate) and target (point), but it's vague about the specific type of point (geodetic) and doesn't distinguish from sibling tools like 'calculate_geodetic_distance' or 'calculate_geodetic_area'. It provides a basic purpose but lacks specificity and differentiation.

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. The description doesn't mention any context, prerequisites, or exclusions, such as when to choose this over other geodetic or geometric tools in the sibling list. This leaves the agent without usage direction.

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