Skip to main content
Glama
Sign In
QGIS MCP Server

QGIS MCP Server

by awheeler262
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Layer Order

set_layer_order
Idempotent

Define the draw order of QGIS layers by providing an ordered list of layer IDs from top to bottom; unlisted layers keep their existing slots and any custom draw order is cleared.

Instructions

Reorder layer tree nodes; tree order is draw order. layer_ids is the ordered list of layer ids from top (drawn last) to bottom; unlisted layers keep their slots. Clears any custom draw order (it freezes a snapshot list — layers added later would silently draw behind everything).

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_ids": "<layer_ids>"
    },
    "name": "set_layer_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
layer_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Description adds significant behavioral details beyond the idempotent hint: it explains that unlisted layers keep their slots, that custom draw order is cleared, and that layers added later silently draw behind everything. No contradiction with annotations.

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 extremely concise, using three short sentences that cover purpose, parameter explanation, and critical side effect. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given low complexity (single parameter, no output schema), the description is complete. It covers the core operation, parameter semantics, and important behavioral consequences. Fully sufficient for correct tool invocation.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining the layer_ids parameter as an ordered list from top (drawn last) to bottom. Also clarifies behavior for unlisted layers, which adds essential meaning.

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 tool reorders layer tree nodes and explicitly ties tree order to draw order. It distinguishes from siblings like set_layer_visibility or move_layer_to_group by focusing on reordering within the tree hierarchy.

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

Usage Guidelines4/5

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

Provides good context on when to use (reorder layers) and a crucial behavioral note about clearing custom draw order. Lacks explicit when-not-to-use or alternatives, but the context is sufficient for informed selection.

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