Skip to main content
Glama

envelope

Calculate the bounding box for any geometry to define its spatial extent for mapping and analysis.

Instructions

Get bounding box of a geometry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geometryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'envelope' MCP tool, which computes the bounding box (envelope) of an input geometry provided as WKT string using Shapely library and returns the result as WKT with status information.
    @gis_mcp.tool()
    def envelope(geometry: str) -> Dict[str, Any]:
        """Get bounding box of a geometry."""
        try:
            from shapely import wkt
            geom = wkt.loads(geometry)
            result = geom.envelope
            return {
                "status": "success",
                "geometry": result.wkt,
                "message": "Envelope created successfully"
            }
        except Exception as e:
            logger.error(f"Error creating envelope: {str(e)}")
            raise ValueError(f"Failed to create envelope: {str(e)}")
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 a read operation ('Get'), implying it's likely non-destructive, but does not specify output format, error handling, or any constraints (e.g., input geometry validity). This leaves gaps in understanding the tool's behavior beyond the basic action.

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 directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for its simplicity, earning full marks for conciseness.

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 (single parameter, no annotations) and the presence of an output schema, the description is minimally adequate. It covers the basic action but lacks details on usage, parameters, and behavioral context, making it incomplete for optimal agent understanding despite the output schema handling return values.

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

Parameters3/5

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

The description adds no parameter semantics beyond the input schema, which has 0% description coverage for the single parameter 'geometry'. Since schema coverage is low, the description does not compensate by explaining what 'geometry' should be (e.g., format, examples), resulting in minimal added value. With 0 parameters explicitly mentioned, the baseline is not fully met due to the coverage gap.

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 ('bounding box of a geometry'), making the purpose specific and understandable. However, it does not differentiate from sibling tools like 'get_bounds' or 'minimum_rotated_rectangle', which might have overlapping or related functionality, so it misses full sibling distinction.

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. With many sibling tools in the list (e.g., 'get_bounds', 'get_centroid'), there is no indication of context, prerequisites, or exclusions for using 'envelope', leaving 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