Skip to main content
Glama
Sign In
QGIS MCP Server

QGIS MCP Server

by LuiccianDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Set Active Layer

set_active_layer
Idempotent

Selects the active layer in the QGIS layer panel using its layer ID, so agents can direct subsequent edits, styling, and processing to the intended layer.

Instructions

Set the active layer in the QGIS layer panel by layer ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "layer_id": "<layer_id>"
    },
    "name": "set_active_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Beyond the idempotentHint annotation, the description does not disclose any behavioral traits (e.g., whether it affects the canvas, triggers events, or is required for other tools). The annotation covers idempotence, but the description adds no further insight.

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 immediately conveys the action and target. No extraneous words.

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?

For a simple setter, the description is adequate but misses the opportunity to explain the importance of the active layer for other QGIS operations (e.g., get_layer_features, zoom_to_layer). No mention of layer existence prerequisite.

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 explains that layer_id is the ID of the layer, which adds meaning beyond the schema's bare type (string). However, it omits details like format (e.g., integer, UUID) or whether it must be an existing layer, leaving ambiguity.

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 action (set), the resource (active layer), and the method (by layer ID). It distinguishes itself from the sibling tool get_active_layer which retrieves the active layer.

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 (e.g., set_layer_visibility, set_layer_property). It does not mention prerequisites or context.

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

Deploy Server

Other Tools