Skip to main content
Glama

get_area

Calculate the area of a geometric shape using GIS data. Input geometry to obtain accurate spatial measurements for analysis and planning.

Instructions

Get the area of a geometry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geometryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_area' MCP tool. It takes a WKT geometry string, loads it with shapely.wkt.loads, computes the area using geom.area, and returns a dictionary with status, area, and message. Errors are logged and raised.
    @gis_mcp.tool()
    def get_area(geometry: str) -> Dict[str, Any]:
        """Get the area of a geometry."""
        try:
            from shapely import wkt
            geom = wkt.loads(geometry)
            return {
                "status": "success",
                "area": float(geom.area),
                "message": "Area calculated successfully"
            }
        except Exception as e:
            logger.error(f"Error calculating area: {str(e)}")
            raise ValueError(f"Failed to calculate area: {str(e)}")
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't mention whether this is a read-only operation, what units the area is returned in, how geometry input should be formatted, or any error conditions. This leaves critical behavioral aspects unspecified.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a simple calculation tool and front-loads the essential information.

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?

While an output schema exists (which relieves the description from explaining return values), this is a parameterized tool with no annotations and 0% schema description coverage. The description doesn't provide enough context about geometry format, supported types, or behavioral aspects to make this tool usable without additional documentation.

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

Parameters1/5

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

Schema description coverage is 0%, meaning the single parameter 'geometry' has no documentation in the schema. The description adds no information about what format the geometry should be in (e.g., GeoJSON, WKT), what types of geometries are supported, or any constraints. This fails to compensate for the complete lack of schema documentation.

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 verb ('Get') and resource ('area of a geometry'), making the purpose immediately understandable. It distinguishes itself from siblings like 'get_length' or 'get_bounds' by specifying area calculation. However, it doesn't explicitly differentiate from 'calculate_geodetic_area', which might be a more specialized alternative.

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?

The description provides no guidance on when to use this tool versus alternatives like 'calculate_geodetic_area' or other geometry measurement tools. It doesn't mention prerequisites, context, or exclusions, leaving the agent with minimal 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