Skip to main content
Glama

get_layers

Retrieve all layers from the current QGIS project to access and manage spatial data for analysis and visualization.

Instructions

Retrieve all layers in the current project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_layers' that connects to QGIS socket server and forwards the command, returning JSON response.
    @mcp.tool()
    def get_layers(ctx: Context) -> str:
        """Retrieve all layers in the current project."""
        qgis = get_qgis_connection()
        result = qgis.send_command("get_layers")
        return json.dumps(result, indent=2)
  • Core QGIS plugin handler that implements get_layers by iterating over project layers and collecting detailed information.
    def get_layers(self, **kwargs):
        """Get all layers in the project"""
        project = QgsProject.instance()
        layers = []
        
        for layer_id, layer in project.mapLayers().items():
            layer_info = {
                "id": layer_id,
                "name": layer.name(),
                "type": self._get_layer_type(layer),
                "visible": project.layerTreeRoot().findLayer(layer_id).isVisible()
            }
            
            # Add type-specific information
            if layer.type() == QgsMapLayer.VectorLayer:
                layer_info.update({
                    "feature_count": layer.featureCount(),
                    "geometry_type": layer.geometryType()
                })
            elif layer.type() == QgsMapLayer.RasterLayer:
                layer_info.update({
                    "width": layer.width(),
                    "height": layer.height()
                })
                
            layers.append(layer_info)
        
        return layers
  • Registration of command handlers in QGIS plugin server, including 'get_layers' mapped to self.get_layers method.
    handlers = {
        "ping": self.ping,
        "get_qgis_info": self.get_qgis_info,
        "load_project": self.load_project,
        "get_project_info": self.get_project_info,
        "execute_code": self.execute_code,
        "add_vector_layer": self.add_vector_layer,
        "add_raster_layer": self.add_raster_layer,
        "get_layers": self.get_layers,
        "remove_layer": self.remove_layer,
        "zoom_to_layer": self.zoom_to_layer,
        "get_layer_features": self.get_layer_features,
        "execute_processing": self.execute_processing,
        "save_project": self.save_project,
        "render_map": self.render_map,
        "create_new_project": self.create_new_project,
    }
  • Helper function to manage persistent socket connection to the QGIS MCP plugin server.
    def get_qgis_connection():
        """Get or create a persistent Qgis connection"""
        global _qgis_connection
        
        # If we have an existing connection, check if it's still valid
        if _qgis_connection is not None:
            # Test if the connection is still alive with a simple ping
            try:
                # Just try to send a small message to check if the socket is still connected
                _qgis_connection.sock.sendall(b'')
                return _qgis_connection
            except Exception as e:
                # Connection is dead, close it and create a new one
                logger.warning(f"Existing connection is no longer valid: {str(e)}")
                try:
                    _qgis_connection.disconnect()
                except Exception:
                    pass
                _qgis_connection = None
        
        # Create a new connection if needed
        if _qgis_connection is None:
            _qgis_connection = QgisMCPServer(host="localhost", port=9876)
            if not _qgis_connection.connect():
                logger.error("Failed to connect to Qgis")
                _qgis_connection = None
                raise Exception("Could not connect to Qgis. Make sure the Qgis plugin is running.")
            logger.info("Created new persistent connection to Qgis")
        
        return _qgis_connection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, and the description only states 'Retrieve all layers' without any details on side effects, permissions, or return format. For a read-only operation, the description is minimal.

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, concise sentence with no wasted words, front-loading the core purpose.

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 has no parameters and no output schema, the description is minimally adequate. However, it could be improved by indicating the return format, such as 'returns a list of layer names or objects'.

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

Parameters4/5

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

There are no parameters, so the description adds no parameter-specific meaning. Schema coverage is 100%, and baseline for zero-param tools is 4.

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

Purpose5/5

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

The description clearly states the verb 'Retrieve', the resource 'all layers', and the context 'in the current project'. It distinguishes from sibling tools like add_raster_layer and get_layer_features.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing a list of layers but provides no explicit guidance on when to use this tool versus alternatives or any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.