Skip to main content
Glama
Sign In
QGIS MCP

QGIS MCP

by lefcgis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Save Style QML

save_style_qml

Save a QGIS layer's style configuration to a portable QML file for reuse or sharing.

Instructions

Save a layer's style to a QGIS QML file.

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>",
      "path": "<path>"
    },
    "name": "save_style_qml"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
layer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are present, and the description lacks behavioral details such as whether existing files are overwritten, if directories are created, or what happens if the layer has no style.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but too sparse to be effective. It does not waste words, but it lacks necessary detail.

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?

With only 2 parameters and no schema descriptions or output schema, the description fails to provide essential context about the style file content, return value, or error handling.

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?

The input schema has 0% description coverage. The description does not explain the parameters 'path' or 'layer_id', leaving the agent without guidance on required format or source of the layer ID.

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 'Save', the resource 'a layer's style', and the output format 'QGIS QML file'. It is specific and distinguishes from sibling tools like apply_style_qml.

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?

No guidance is provided on when to use this tool versus alternatives, such as apply_style_qml or set_layer_style. Prerequisites or conditions are not mentioned.

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